Method for determining link availability for IAB node, and node using same

ABSTRACT

The present specification provides a method for transmitting guard symbol information, which is performed by a node in a wireless communication system, the method comprising: determining the guard symbol information, the guard symbol information indicating the number of guard symbols, desired by the node, associated with switching between a mobile terminal (MT) operation and a distributed unit (DU) operation; and transmitting the guard symbol information to a parent node, the guard symbol being a symbol not used on the basis of a transition between the MT operation and the DU operation.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a Continuation of U.S. patent application Ser. No. 17/571,024, filed on Jan. 7, 2022, which is a Continuation Bypass of International Application No. PCT/KR2020/008961, filed on Jul. 8, 2020, which claims the benefit of U.S. Provisional Application No. 62/888,395, filed on Aug. 16, 2019, and Korean Patent Application Nos. 10-2019-0082326, filed on Jul. 8, 2019, 10-2019-0128977, filed on Oct. 17, 2019, 10-2019-0147040, filed on Nov. 15, 2019, 10-2020-0043007, filed on Apr. 8, 2020 and 10-2020-0057931, filed on May 14, 2020, the contents of which are all hereby incorporated by reference herein in their entirety.

FIELD OF THE DISCLOSURE

The present specification relates to wireless communication.

RELATED ART

As a wider range of communication devices require larger communication capacities, the need for mobile broadband communication that is more enhanced than the existing Radio Access Technology (RAT) is rising. Additionally, massive Machine Type Communications (massive MCT), which connects multiple devices and objects so as to provide various services regardless of time and place, is also one of the most important issues that are to be considered in the next generation communication. Moreover, discussions are made on services/terminals (or user equipment (UE)) that are sensitive to reliability and latency. And, discussions are made on the adoption of a next generation radio access technology that is based on the enhanced mobile broadband communication, massive MTC, Ultra-Reliable and Low Latency Communication (URLLC), and so on. And, for convenience, the corresponding technology will be referred to as a new radio access technology (new RAT or NR).

On the other hand, integrated access and backhaul link may be provided. Hereinafter, in this specification, features for Integrated Access Backhaul (IAB) will be provided.

SUMMARY OF THE DISCLOSURE Technical Solutions

According to an embodiment of the present specification, a method and a node using the same are provided. The method and the node may comprise transmitting, to a parent node, the guard symbol information, wherein the guard symbol information informs each of a number of guard symbols related to switching, which is desired by the node, between a mobile terminal (MT) operation and a distributed unit (DU) operation, and wherein the guard symbol is a symbol not used based on a transition between the MT operation and the DU operation.

Effects of the Disclosure

According to this specification, a feature for the guard symbol is provided, and stable switching between the MT operation and the DU operation may be provided, and thus, communication stability may be increased.

The effects that can be obtained through a specific example of the present specification are not limited to the effects listed above. For example, there may be various technical effects that a person having ordinary skill in the related art can understand or derive from the present specification. Accordingly, specific effects of the present specification are not limited to those explicitly described in the present specification, and may include various effects that can be understood or derived from the technical features of the present specification.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates another example of a wireless communication system to which technical features of the present disclosure are applicable.

FIG. 2 illustrates physical channels used in 3GPP systems and general signal transmission.

FIG. 3 schematically illustrates a synchronization signal and PBCH block (SS/PBCH block).

FIG. 4 illustrates a method of acquiring timing information by a UE.

FIG. 5 illustrates an example of a system information acquisition process of a UE.

FIG. 6 illustrates the random access procedure.

FIG. 7 illustrates the power ramping counter.

FIG. 8 illustrates the concept of a threshold of SS blocks for RACH resource association.

FIG. 9 illustrates a frame structure applicable in NR.

FIG. 10 illustrates an example of a frame structure for the new radio access technology (new RAT).

FIG. 11 shows examples of 5G usage scenarios to which the technical features of the present specification can be applied.

FIG. 12 schematically illustrates an example of integrated access and backhaul links.

FIG. 13 schematically illustrates an example of a link between a DgNB, an RN, and a UE.

FIG. 14 schematically shows an example of a backhaul link and an access link.

FIG. 15 schematically shows an example of a parent link and a child link.

FIG. 16 schematically shows a configuration between nodes.

FIG. 17 schematically shows an example in which the MT and DU of the IAB node are configured with a plurality of CCs.

FIG. 18 is a flowchart of a method of transmitting and receiving information about a guard symbol, according to another embodiment of the present specification.

FIG. 19 schematically shows an example of timing adjustment.

FIG. 20 is an example of a method for determining link availability of an MT based on link availability configured to a DU.

FIGS. 21 to 24 schematically show an example for determining the availability of a resource based on the relationship between the DU operation and the MT operation.

FIG. 25 is an example of a method for determining link availability of a DU based on link availability configured to the MT.

FIGS. 26 to 29 schematically show another example for determining the availability of a resource based on the relationship between the DU operation and the MT operation.

FIG. 30 is an example of a method for determining link availability based on link availability configured in each of the DU side and the MT side of the IAB node.

FIGS. 31 to 34 schematically illustrate an example of a gap time required for switching when performing switching between a DU operation and an MT operation.

FIGS. 35 and 36 schematically show an example of link availability.

FIG. 37 schematically shows an example of MT resource availability determination.

FIG. 38 is a flowchart of a method for transmitting guard symbol information, according to an embodiment of the present specification.

FIG. 39 schematically illustrates an example of a method of transmitting a guard symbol MAC CE.

FIG. 40 schematically illustrates another example of a method of transmitting a guard symbol MAC CE.

FIG. 41 schematically illustrates another example of a method of transmitting a guard symbol MAC CE.

FIG. 42 schematically illustrates another example of a method of transmitting a guard symbol MAC CE.

FIG. 43 schematically illustrates another example of a method of transmitting a guard symbol MAC CE.

FIG. 44 schematically illustrates another example of a method of transmitting a guard symbol MAC CE.

FIG. 45 schematically illustrates another example of a method of transmitting a guard symbol MAC CE.

FIG. 46 is a flowchart of a method of transmitting information about a guard symbol from the viewpoint of a (child) node, according to an embodiment of the present specification.

FIG. 47 is a block diagram of an example of an apparatus for transmitting information about a guard symbol from the viewpoint of a (child) node, according to an embodiment of the present specification.

FIG. 48 is a flowchart of a method of receiving information about a guard symbol from the viewpoint of a (parent) node, according to an embodiment of the present specification.

FIG. 49 is a block diagram of an example of an apparatus for receiving information about a guard symbol from the perspective of a (parent) node, according to an embodiment of the present specification.

FIG. 50 shows an exemplary communication system (1), according to an embodiment of the present specification.

FIG. 51 shows an exemplary wireless device to which the present specification can be applied.

FIG. 52 shows another example of a wireless device applicable to the present specification.

FIG. 53 shows a signal process circuit for a transmission signal according to an embodiment of the present specification.

FIG. 54 shows another example of a wireless device according to an embodiment of the present specification.

FIG. 55 shows a hand-held device to which the present specification is applied.

FIG. 56 shows a vehicle or an autonomous vehicle to which the present specification is applied.

FIG. 57 is a diagram illustrating an example of a communication structure that can be provided in a 6G system.

DESCRIPTION OF EXEMPLARY EMBODIMENTS

In the present specification, “A or B” may mean “only A”, “only B” or “both A and B”. In other words, in the present specification, “A or B” may be interpreted as “A and/or B”. For example, in this specification, “A, B or C” refers to “only A”, “only B”, “only C”, or “any combination of A, B and C”.

A forward slash (/) or comma used herein may mean “and/or”. For example, “A/B” may mean “A and/or B”. Accordingly, “A/B” may mean “only A”, “only B”, or “both A and B”. For example, “A, B, C” may mean “A, B, or C”.

In the present specification, “at least one of A and B” may mean “only A”, “only B”, or “both A and B”. In addition, in the present specification, the expression “at least one of A or B” or “at least one of A and/or B” can be interpreted the same as “at least one of A and B”.

In addition, in the present specification, “at least one of A, B and C” means “only A”, “only B”, “only C”, or “any combination of A, B and C”. In addition, “at least one of A, B or C” or “at least one of A, B and/or C” can mean “at least one of A, B and C”.

In addition, parentheses used in the present specification may mean “for example”. Specifically, when described as “control information (PDCCH)”, “PDCCH” may be proposed as an example of “control information”. In other words, “control information” of the present specification is not limited to “PDCCH”, and “PDDCH” may be suggested as an example of “control information”. In addition, even when described as “control information (i.e., PDCCH)”, “PDCCH” may be proposed as an example of “control information”.

In the present specification, technical features that are individually described in one drawing may be implemented individually or at the same time.

FIG. 1 illustrates another example of a wireless communication system to which technical features of the present disclosure are applicable.

Specifically, FIG. 1 shows a system architecture based on a 5G new radio access technology (NR) system. The entity used in the 5G NR system (hereinafter, simply referred to as “NR”) may absorb some or all of the functions of the entities introduced in FIG. 1 (e.g. eNB, MME, S-GW). The entity used in the NR system may be identified by the name “NG” for distinction from the LTE.

Referring to FIG. 1 , the wireless communication system includes one or more UE 11, a next-generation RAN (NG-RAN) and a 5th generation core network (5GC). The NG-RAN consists of at least one NG-RAN node. The NG-RAN node is an entity corresponding to the BS 20 shown in FIG. 1 . The NG-RAN node consists of at least one gNB 21 and/or at least one ng-eNB 22. The gNB 21 provides NR user plane and control plane protocol terminations towards the UE 11. The ng-eNB 22 provides E-UTRA user plane and control plane protocol terminations towards the UE 11.

The 5GC includes an access and mobility management function (AMF), a user plane function (UPF) and a session management function (SMF). The AMF hosts the functions, such as NAS security, idle state mobility handling, etc. The AMF is an entity including the functions of the conventional MME. The UPF hosts the functions, such as mobility anchoring, protocol data unit (PDU) handling. The UPF an entity including the functions of the conventional S-GW. The SMF hosts the functions, such as UE IP address allocation, PDU session control.

The gNBs and ng-eNBs are interconnected with each other by means of the Xn interface. The gNBs and ng-eNBs are also connected by means of the NG interfaces to the 5GC, more specifically to the AMF by means of the NG-C interface and to the UPF by means of the NG-U interface.

A structure of a radio frame in NR is described. In LTE/LTE-A, one radio frame consists of 10 subframes, and one subframe consists of 2 slots. A length of one subframe may be 1 ms, and a length of one slot may be 0.5 ms. Time for transmitting one transport block by higher layer to physical layer (generally over one subframe) is defined as a transmission time interval (TTI). A TTI may be the minimum unit of scheduling.

Unlike LTE/LTE-A, NR supports various numerologies, and accordingly, the structure of the radio frame may be varied. NR supports multiple subcarrier spacings in frequency domain. Table 1 shows multiple numerologies supported in NR. Each numerology may be identified by index μ.

TABLE 1 Subcarrier Cyclic Supported Supported for μ spacing (kHz) prefix for data synchronization 0 15 Normal Yes Yes 1 30 Normal Yes Yes 2 60 Normal, Yes No Extended 3 120 Normal Yes Yes 4 240 Normal No Yes

Referring to Table 1, a subcarrier spacing may be set to any one of 15, 30, 60, 120, and 240 kHz, which is identified by index μ. However, subcarrier spacings shown in Table 1 are merely exemplary, and specific subcarrier spacings may be changed. Therefore, each subcarrier spacing (e.g., μ=0, 1 . . . 4) may be represented as a first subcarrier spacing, a second subcarrier spacing . . . Nth subcarrier spacing. Referring to Table 1, transmission of user data (e.g., physical uplink shared channel (PUSCH), physical downlink shared channel (PDSCH)) may not be supported depending on the subcarrier spacing. That is, transmission of user data may not be supported only in at least one specific subcarrier spacing (e.g., 240 kHz).

In addition, referring to Table 1, a synchronization channel (e.g., a primary synchronization signal (PSS), a secondary synchronization signal (SSS), a physical broadcast channel (PBCH)) may not be supported depending on the subcarrier spacing. That is, the synchronization channel may not be supported only in at least one specific subcarrier spacing (e.g., 60 kHz).

In NR, a number of slots and a number of symbols included in one radio frame/subframe may be different according to various numerologies, i.e., various subcarrier spacings. Table 2 shows an example of a number of OFDM symbols per slot, slots per radio frame, and slots per subframe for normal cyclic prefix (CP).

TABLE 2 Number of Number of slots Number of slots μ symbols per slot per radio frame per subframe 0 14 10 1 1 14 20 2 2 14 40 4 3 14 80 8 4 14 160 16

Referring to Table 2, when a first numerology corresponding to μ=0 is applied, one radio frame includes 10 subframes, one subframe corresponds to one slot, and one slot consists of 14 symbols. In the present disclosure, a symbol refers to a signal transmitted during a specific time interval. For example, a symbol may refer to a signal generated by OFDM processing. That is, a symbol in the present disclosure may refer to an OFDM/OFDMA symbol, or SC-FDMA symbol, etc. A CP may be located between each symbol. Hereinafter, a physical channel and a signal transmission process will be described.

FIG. 2 illustrates physical channels used in 3GPP systems and general signal transmission.

In a wireless communication system, a UE receives information from an eNB on downlink and transmits information to the eNB on uplink. Information transmitted/received between the eNB and the UE includes data and various types of control information and there are various physical channels according to types/purposes of information transmitted/received by the eNB and the UE.

A UE performs initial cell search such as synchronization with an eNB when it is powered on or newly enters a cell (S11). To this end, the UE receives a primary synchronization channel (PSCH) and a secondary synchronization channel (SSCH) from the eNB to synchronize with the eNB and acquires information such as cell identity (ID). In addition, the UE may receive a physical broadcast channel (PBCH) from the eNB to acquire broadcast information in the cell. Further, the UE may receive a downlink reference signal (DL RS) in the initial cell search stage to check a downlink channel state.

Upon completion of initial cell search, the UE may receive a physical downlink control channel (PDCCH) and a physical downlink shared channel (PDSCH) corresponding thereto to acquire more specific system information (S12).

Thereafter, the UE may perform a random access procedure to complete access to the eNB (S13 to S16). Specifically, the UE may transmit a preamble through a physical random access channel (PRACH) (S13) and receive a random access response (RAR) for the preamble through the PDCCH and the PDSCH corresponding thereto (S14). Then, the UE may transmit a physical uplink shared channel (PUSCH) using scheduling information in the RAR (S15) and perform a contention resolution procedure with respect to the PDCCH and the PDSCH corresponding thereto (S16).

Upon execution of the above-described procedures, the UE may perform PDCCH/PDSCH reception (17) and PUSCH/PUCCH (Physical Uplink Control Channel) transmission (S18) as a general uplink/downlink signal transmission procedure. Control information transmitted from the UE to the eNB is referred to as uplink control information (UCI). The UCI includes hybrid automatic repeat and request acknowledgement/negative-ACK (HARQ ACK/NACK), a scheduling request (SR), and channel state information (CSI). The CSI includes a channel quality indicator (CQI), a precoding matrix indicator (PMI), and a rank indication (RI). Although the UCI is transmitted through a PUCCH in general, it may be transmitted through a PUSCH when control information and data need to be simultaneously transmitted. Further, the UE may aperiodically transmit the UCI through the PUSCH in response to a request/instruction of a network.

Hereinafter, cell search will be described.

Cell search is a procedure through which a UE acquires time and frequency synchronization with a cell and detects a physical layer cell ID of the cell. To perform cell search, the UE receives a primary synchronization signal (PSS) and a secondary synchronization signal (SSS).

The cell search procedure of the UE cam be summarized in in Table 3.

TABLE 3 Signal type Operation Step 1 PSS SS/PBCH block (SSB) symbol timing acquisition Cell ID search in cell ID group (3 hypothesis) Step 2 SSS Cell ID group detection (336 hypothesis) Step 3 PBCH DMRS SSB index and half frame index (slot and frame boundary detection) Step 4 PBCH Time information (80 ms, SFN, SSB index, HF) RMSI CORESET/search space configuration Step 5 PDCCH and Cell access information PDSCH RACH configuration

FIG. 3 schematically illustrates a synchronization signal and PBCH block (SS/PBCH block). Referring to FIG. 3 , the SS/PBCH block includes a PSS and an SSS each occupying one symbol and 127 subcarriers, and a PBCH occupying 3 OFDM symbols and 240 subcarriers with an unused part for the SSS remaining on one symbol. Periodicity of the SS/PBCH block may be set by a network, and a temporal position at which the SS/PBCH block can be transmitted is determined by a subcarrier spacing.

Polar coding is used for the PBCH. A UE can assume a band-specific subcarrier spacing for the SS/PBCH block unless a network sets the UE such that the UE assumes a different subcarrier spacing.

The PBCH symbols carry a frequency-multiplexed DMRS thereof. QPSK modulation is used for the PBCH.

1008 unique physical layer cell IDs are given according to the following equation 1. N _(ID) ^(cell)=3N _(ID) ⁽¹⁾ +N _(ID) ⁽²⁾  [Equation 1]

(Here, NID(1)∈{0, 1, . . . , 335} and NID(2)∈{0, 1, 2}.)

Meanwhile, a PSS sequence dPSS(n) for the PSS is defined by the following equation 2. d _(PSS)(n)=1−2x(m)  [Equation 2] m=(n+43N _(ID) ⁽²⁾)mod 127

0≤n<127

(Here, x(i+7)=(x(i+4)+x(i))mod 2 and [x(6) x(5) x(4) x(3) x(2) x(1) x(0)]=[1 1 1 0 1 1 0].)

The aforementioned sequence can be mapped to physical resources illustrated in FIG. 2 .

Meanwhile, an SSS sequence dSSS(n) for the SSS is defined by the following equation 3.

$\begin{matrix} {{{d_{SSS}(n)} = \text{ }{\left\lbrack {1 - {2{x_{0}\left( {\left( {n + m_{0}} \right){mod}\ 127} \right)}}} \right\rbrack\left\lbrack {1 - {2{x_{1}\left( {\left( {n + m_{1}} \right){mod}\ 127} \right.}}} \right\rbrack}}{{m0} = {{{15} \star \frac{N_{ID}^{(1)}}{112}} + {{+ 5}N_{ID}^{(2)}}}}{m_{1} = {N_{ID}^{(1)}{mod}112}}{0 \leq n < {127}}} & \left\lbrack {{Equation}3} \right\rbrack \end{matrix}$ x ₀(i+7)=(x ₀(i+4)+x ₀(i))mod 2

(Here, x₁(i+7)=(x₁(i+1)+x₁(i))mod 2 and [x₀(6) x₀(5) x₀(4) x₀(3) x₀(2) x₀(1) x₀(0)]=[0 0 0 0 0 0 1] [x₁(6) x₁(5) x₁(4) x₁(3) x₁(2) x₁(1) x₁(0)]=[0 0 0 0 0 0 1].)

The aforementioned sequence can be mapped to physical resources illustrated in FIG. 3 .

For a half frame with SS/PBCH blocks, the first symbol indexes for candidate S S/PBCH blocks may be determined according to the subcarrier spacing of SS/PBCH bloc ks as follows.

Case A—15 kHz subcarrier spacing: the first symbols of the candidate SS/PBCH blocks have indexes of {2, 8}+14*n. For carrier frequencies smaller than or equal to 3 GHz, n=0, 1. For carrier frequencies larger than 3 GHz and smaller than or equal to 6 GHz, n=0, 1, 2, 3.

Case B—30 kHz subcarrier spacing: the first symbols of the candidate SS/PBCH blocks have indexes {4, 8, 16, 20}+28*n. For carrier frequencies smaller than or equal to 3 GHz, n=0. For carrier frequencies larger than 3 GHz and smaller than or equal to 6 GHz, n=0, 1.

Case C—30 kHz subcarrier spacing: the first symbols of the candidate SS/PBCH blocks have indexes {2, 8}+14*n. For carrier frequencies smaller than or equal to 3 GHz, n=0, 1. For carrier frequencies larger than 3 GHz and smaller than or equal to 6 GHz, n=0, 1, 2, 3.

Case D—120 kHz subcarrier spacing: the first symbols of the candidate SS/PBCH blocks have indexes {4, 8, 16, 20}+28*n. For carrier frequencies larger than 6 GHz, n=0, 1, 2, 3, 5, 6, 7, 8, 10, 11, 12, 13, 15, 16, 17, 18.

Case E—240 kHz subcarrier spacing: the first symbols of the candidate SS/PBCH blocks have indexes {8, 12, 16, 20, 32, 36, 40, 44}+56*n. For carrier frequencies larger than 6 GHz, n=0, 1, 2, 3, 5, 6, 7, 8.

The candidate SS/PBCH blocks in a half frame may be indexed in an ascending order in time from 0 to L−1. A UE needs to determine the 2 LSBs, for L=4, or the 3 LSBs, for L>4, of a SS/PBCH block index per half frame from one-to-one mapping with an index of the DM-RS sequence transmitted in the PBCH. For L=64, the UE needs to determine the 3 MSBs of the SS/PBCH block index per half frame by PBCH payload bits ā_(Ā+5) , ā_(Ā+6) , ā_(Ā+7) .

A UE can be configured by higher layer parameter “SSB-transmitted-SIB1”, indexes of SS/PBCH blocks for which the UE cannot receive other signals or channels in REs that overlap with REs corresponding to the SS/PBCH blocks. A UE can also be configured per serving cell, by higher layer parameter “SSB-transmitted”, indexes of SS/PBCH blocks for which the UE cannot receive other signals or channels in REs that overlap with REs corresponding to the SS/PBCH blocks. A configuration by “SSB-transmitted” may override a configuration by “SSB-transmitted-SIB1”. A UE can be configured per serving cell by higher layer parameter “SSB-periodicityServingCell” a periodicity of the half frames for reception of SS/PBCH blocks per serving cell. If the UE is not configured a periodicity of the half frames for receptions of SS/PBCH blocks, the UE may assume a periodicity of a half frame. A UE may assume that the periodicity is same for all SS/PBCH blocks in the serving cell.

FIG. 4 illustrates a method of acquiring timing information by a UE.

Firstly, the UE may acquire 6-bit SFN information via master information block (MIB) received in a PBCH. Further, the UE may acquire 4-bit SFN in a PBCH transport block.

Secondly, the UE may acquire 1-bit half frame indication as a part of a PBCH payload. For below 3 GHz, half frame indication may be further implicitly signaled as a part of a PBCH DMRS for Lmax=4.

Lastly, the UE may acquire an SS/PBCH block index by a DMRS sequence and the PBCH payload. That is, 3 LSBs of an SS block index can be acquired by the DMRS sequence within a period of 5 ms. Further, 3 MSBs of timing information are carried explicitly in the PBCH payload (for above 6 GHz).

For initial cell selection, a UE may assume that half frames with SS/PBCH blocks occur with a periodicity of 2 frames. Upon detection of an SS/PBCH block, the UE determines that a control resource set for Type0-PDCCH common search space is present if k_(SSB)<23 for FR1 and if k_(SSB)<11 for FR2. The UE determines that a control resource set for Type0-PDCCH common search space is not present if k_(SSB)>23 for FR1 and of k_(SSB)>11 for FR2.

For a serving cell without transmission of SS/PBCH blocks, a UE acquires time and frequency synchronization with the serving cell based on receptions of SS/PBCH blocks on the PCell, or on the PSCell, of the cell group for the serving cell.

Hereinafter, acquisition of system information (SI) will be described.

System information (SI) is divided into MasterInformationBlock (MIB) and a number of SystemInformationBlocks (SIB s) where:

-   -   the MIB is always transmitted on a BCH with a periodicity of 80         ms and repetitions made within 80 ms and it includes parameters         necessary to acquire SystemInformationBlockType1 (SIB1) from the         cell;     -   SIB1 is transmitted on a DL-SCH with a periodicity and         repetitions. SIB1 includes information regarding the         availability and scheduling (e.g., periodicity, SI-window size)         of other SIBs. It also indicates whether they (i.e., other SIBs)         are provided via periodic broadcast basis or only on-demand         basis. If other SIBs are provided on-demand, when SIB1 includes         information for the UE to perform SI request;     -   SIBs other than SIB1 are carried in SystemInformation (SI)         messages, which are transmitted on the DL-SCH. Each SI message         is transmitted within periodically occurring time domain windows         (referred to as SI-windows);     -   For PSCell and SCells, RAN provides the required SI by dedicated         signaling. Nevertheless, the UE needs to acquire MIB of the         PSCell to get SFN timing of the SCG (which may be different from         MCG). Upon change of relevant SI for SCell, RAN releases and         adds the concerned SCell. For PSCell, SI can only be changed         with Reconfiguration with Sync.

FIG. 5 illustrates an example of a system information acquisition process of a UE.

Referring to FIG. 5 , the UE may receive MIB from a network and then receive SIB1. Then, the UE may transmit a system information request to the network and receive a SystemInformation message from the network in response to the system information request.

The UE may apply a system information acquisition procedure to acquire access stratum (AS) and non-access stratum (NAS) information.

The UE in RRC_IDLE and RRC_INACTIVE states needs to ensure having a valid version of (at least) MIB, SIB1, and SystemInformationBlockTypeX (depending on support of the concerned RATs for UE controlled mobility).

The UE in RRC_CONNECTED state needs to ensure having a valid version of MIB, SIB1, and SystemInformationBlockTypeX (depending on support of mobility towards the concerned RATs).

The UE needs to store relevant SI acquired from the currently camped/serving cell. A version of the SI acquired and stored by the UE remains valid only for a certain time. The UE can use such a stored version of the SI, for example, after cell re-selection, upon return from out of coverage or after system information change indication.

Hereinafter, random access (RA) will be described.

A random access procedure of a UE can be summarized in Table 4.

TABLE 4 Signal type Operation/acquired information Step 1 PRACH preamble of Initial beam acquisition uplink Random election of RA-preamble ID Step 2 Random access Timing alignment information response on DL-SCH RA-preamble ID Initial uplink grant, temporary C- RNTI Step 3 Uplink transmission RRC connection request on UL-SCH UE identifier Step 4 Contention resolution C-RNTI on PDCCH for initial access of downlink C-RNTI on PDCCH for UE in RRC_CONNECTED state

FIG. 6 illustrates the random access procedure. Referring to FIG. 6 , firstly, a UE may transmit a PRACH preamble on uplink as message 1 (Msg1) of the random access procedure.

Random access preamble sequences of two different lengths may be supported. A long sequence having a length of 839 is applied with subcarrier spacings of 1.25 kHz and 5 kHz and a short sequence having a length of 139 is applied with subcarrier spacings of 15, 30, 60, and 120 kHz. Long sequences can support unrestricted sets and restricted sets of type A and type B, while short sequences can support unrestricted sets only.

Multiple RACH preamble formats may be defined with one or more RACH OFDM symbols, and different cyclic prefixes (CPs), and a guard time. The PRACH preamble configuration to use may be provided to the UE in the system information.

When there is no response to Msg1, the UE may retransmit the PRACH preamble with power ramping within a predetermined number of times. The UE calculates PRACH transmission power for retransmission of the preamble on the basis of the most recent estimate pathloss and a power ramping counter. If the UE conducts beam switching, the power ramping counter remains unchanged.

FIG. 7 illustrates the power ramping counter.

The UE can perform power ramping for retransmission of a random access preamble on the basis of the power ramping counter. Here, the power ramping counter remains unchanged when the UE performs beam switching during PRACH retransmission, as described above.

Referring to FIG. 7 , when the UE retransmits a random access preamble for the same beam as in a case where the power ramping counter increases from 1 to 2 and from 3 to 4, the UE increases the power ramping counter by 1. However, when the beam has changed, the power ramping counter may not change during PRACH retransmission.

FIG. 8 illustrates the concept of a threshold of SS blocks for RACH resource association.

System information informs the UE of the association between SS blocks and RACH resources. The threshold of the SS blocks for RACH resource association may be based on the RSRP and network configurable. Transmission or retransmission of a RACH preamble may be based on SS blocks that satisfy the threshold. Accordingly, in the example of FIG. 8 , SS block m exceeds the threshold of received power, and thus the RACH preamble is transmitted or retransmitted on the basis of SS block m.

Thereafter, when the UE receives a random access response on a DL-SCH, the DL-SCH may provide timing alignment information, a RA-preamble ID, an initial uplink grant, and a temporary C-RNTI.

Based on this information, the UE may perform uplink transmission on a UL-SCH as message 3 (Msg3) of the random access procedure. Msg3 may include an RRC connection request and a UE ID.

In response, the network may transmit Msg4, which can be treated as a contention resolution message on downlink. The UE can enter an RRC connected state by receiving Msg4.

Hereinafter, the random access procedure will be described in more detail.

Prior to initiation of a physical random access procedure, Layer 1 needs to receive a set of SS/PBCH block indexes from high layers and provide a corresponding set of RSRP measurements to the higher layers.

Prior to initiation of the physical random access procedure, Layer 1 needs to receive the following information from the higher layers.

-   -   Configuration of PRACH transmission parameters (a PRACH preamble         format, time resources, and frequency resources for PRACH         transmission)     -   Parameters for determining root sequences and their cyclic         shifts in a PRACH preamble sequence set (index to logical root         sequence table, cyclic shift (N_(cs)), and set type (an         unrestricted set, restricted set A, and restricted set B)).

From the physical layer perspective, L1 random access procedure encompasses transmission of a random access preamble (Msg1) in a PRACH, a random access response (RAR) message (Msg2) with a PDCCH/PDSCH, and when applicable, transmission of Msg3 PUSCH, and PDSCH for contention resolution.

If a random access procedure is initiated by a PDCCH order to the UE, random access preamble transmission may be with the same subcarrier spacing as a subcarrier spacing for random access preamble transmission initiated by higher layers.

If a UE is configured with two uplink carriers for a serving cell and the UE detects a PDCCH order, the UE may use a UL/SUL indicator field value from the detected PDCCH order to determine an uplink carrier for the corresponding random access preamble transmission.

Hereinafter, the random access preamble will be described in more detail.

Regarding the random access preamble transmission step, the physical random access procedure may be triggered upon request of a PRACH transmission by higher layers or by a PDCCH order. A configuration by higher layers for PRACH transmission may include the following.

-   -   A configuration for PRACH transmission     -   A preamble index, a preamble subcarrier spacing,         P_(PRACH,target), a corresponding RA-RNTI, and a PRACH resources

A preamble may be transmitted using a selected PRACH format with a transmission power P_(PRACH,b,f,c(i)) on the indicated PRACH resources.

A UE may be provided with a number of SS/PBCH blocks associated with one PRACH occasion by a value of a higher layer parameter SSB-perRACH-Occasion. If the value of SSB-perRACH-Occasion is less than 1, one SS/PBCH block can be mapped to consecutive PRACH occasions of 1/SSB-perRACH-Occasions. The UE may be provided with a number of preambles per SS/PBCH by the value of higher layer parameter cb-preamblePerSSB, and the UE may determine a total number of preambles per SSB per PRACH occasion as a multiple of the value of SSB-perRACH-Occasion and the value of cb-preamblePerSSB.

SS/PBCH block indexes may be mapped to PRACH occasions in the following orders.

-   -   First, in ascending order of preamble indexes within a single         PRACH occasion     -   Second, in ascending order of frequency resource indexes for         frequency multiplexed PRACH occasions     -   Third, in ascending order of time resource indexes for time         multiplexed PRACH occasions within a PRACH slot     -   Fourth, in ascending order of indexes for PRACH slots

A period starting from frame 0, for mapping of SS/PBCH blocks to PRACH occasions, is the smallest of PRACH configuration periods {1, 2, 4} equal to or greater than (N_(Tx) ^(SSB)/N_(PRACHperiod) ^(SSB)) where the UE acquires N^(SSB) _(Tx) from higher layer parameter SSB-transmitted-SIB1, and N^(SSB) _(PRACHperiod) is the number of SS/PBCH blocks that can be mapped to one PRACH configuration period.

If a random access procedure is initiated by a PDCCH order, the UE needs to, if requested by higher layers, transmit a PRACH in the first available PRACH occasion for which a time between the last symbol of the PDCCH order reception and the first symbol of the PRACH transmission is equal to or longer than N_(T,2)+Δ_(BWPSwitching)+Δ_(Delay) msec, where N_(T,2) is a time duration of N₂ symbols corresponding to a PUSCH preparation time for PUSCH processing capability 1, Δ_(BWPSwitching) is predefined, and Δ_(Delay)>0.

Hereinafter, the random access response will be described in more detail.

In response to a PRACH transmission, a UE attempts to detect a PDCCH with a corresponding RA-RNTI during a window controlled by higher layers. The window may start at the first symbol of the earliest control resource set the UE is configured for Type1-PDCCH common search space that is at least ((ΔEN_(slot) ^(subframe,μ)EN_(symb) ^(slot))/T_(sf)) symbols after the last symbol of preamble sequence transmission. The length of the window in number of slots, based on the subcarrier spacing for Type0-PDCCH common search space may be provided by higher layer parameter rar-WindowLength.

If a UE detects a PDCCH with the corresponding RA-RNTI and a corresponding PDSCH including a DL-SCH transport block within the window, the UE can pass the transport block to higher layers. The higher layers can parse the transport block for a random access preamble identity (RAPID) associated with the PRACH transmission. If the higher layers identify the RAPID in RAR message(s) of the DL-SCH transport block, the higher layers can indicate an uplink grant to the physical layer. This may be referred to as a random access response (RAR) uplink grant in the physical layer. If the higher layers do not identify the RAPID associated with the PRACH transmission, the higher layers can indicate to the physical layer to transmit a PRACH. A minimum time between the last symbol of the PDSCH reception and the first symbol of the PRACH transmission is equal to N_(T,1)+Δ_(new)+0.5, where N_(T,1) is a time duration of N₁ symbols corresponding to a PDSCH reception time for PDSCH processing capability 1 and Δ_(new)≥0.

A UE may need to receive the PDCCH with the corresponding RA-RNTI and the corresponding PDSCH including a DL-SCH transport block with the same DM-RS antenna port quasi co-location (QCL) properties, as for a detected SS/PBCH block or a received CSI-RS. If the UE attempts to detect the PDCCH with the corresponding RA-RNTI in response to a PRACH transmission initiated by a PDCCH order, the UE may assume that the PDCCH and the PDCCH order have the same DM-RS antenna port QCL properties.

A RAR uplink grant schedules a PUSCH transmission from the UE (Msg3 PUSCH). The contents of the RAR uplink grant, starting with the MSB and ending with the LSB, are given in Table 5. Table 5 shows a random access response grant configuration field size.

TABLE 5 RAR grant field Number of bits Frequency hopping flag 1 Msg3 PUSCH frequency resource 14 allocation Msg3 PUSCH time resource allocation 4 MCS 4 TPC command for Msg3 PUSCH 3 CSI request 1 Reserved bits 3

Msg3 PUSCH frequency resource allocation is for uplink resource allocation type 1. In case of frequency hopping, based on the indication of the frequency hopping flag, the first one or two bits N_(UL,hop) of the Msg3 PUSCH frequency resource allocation field can be used as hopping information bits. The MCS can be determined from the first 16 indexes of the available MCS index table for the PUSCH.

The TPC command δ_(msg2,b,f,c) is used to set the power of the Msg3 PUSCH and may be interpreted according to the following Table 6.

TABLE 6 TPC Command Value [dB] 0 −6 1 −4 2 −2 3 0 4 2 5 4 6 6 7 8

In a non-contention-based random access procedure, the CSI request field is interpreted to determine whether an aperiodic CSI report is included in the corresponding PUSCH transmission. In a contention-based random access procedure, the CSI request field may be reserved. Unless a UE is configured a subcarrier spacing, the UE receives a subsequent PDSCH using the same subcarrier spacing as that for PDSCH reception which provides a RAR message.

If a UE does not detect the PDCCH with a corresponding RA-RNTI and a corresponding DL-SCH transport block within the window, the UE performs a procedure for random access response reception failure.

Hereinafter, Msg3 PUSCH transmission will be described in more detail.

Regarding Msg3 PUSCH transmission, higher layer parameter msg3-tp indicates to the UE whether or not the UE applies transform precoding, for Msg3 PUSCH transmission. If the UE applies transform precoding to Msg3 PUSCH transmission with frequency hopping, a frequency offset for the second hop may be given in Table 7. Table 7 shows frequency offsets for the second hop for Msg3 PUSCH transmission with frequency hopping.

TABLE 7 Number of PRBs in initial Value of N_(UL,hop) Frequency offset active UL BWP Hopping Bits for 2^(nd) hop N^(size) _(BWP) < 50 0 N^(size) _(BWP)/2 1 N^(size) _(BWP)/4 N^(size) _(BWP) ≥ 50 00 N^(size) _(BWP)/2 01 N^(size) _(BWP)/4 10 −N^(size) _(BWP)/4   11 Reserved

The subcarrier spacing for Msg3 PUSCH transmission may be provided by a higher layer parameter msg3-scs. The UE needs to transmit a PRACH and Msg3 PUSCH on the same uplink carrier of the same serving cell. A UL BWP for Msg3 PUSCH transmission may be indicated by SystemInformationBlockType1. A minimum time between the last symbol of PDSCH reception conveying a RAR and the first symbol of corresponding Msg3 PUSCH transmission scheduled by the RAR in a PDSCH for the UE when the PDSCH and the PUSCH have the same subcarrier spacing may be equal to N_(T,1)+N_(T,2)+N_(TA,max)+0.5 msec. N_(T,1) is a time duration of N₁ symbols corresponding to PDSCH reception time for PDSCH processing capability 1 when an additional PDSCH DM-RS is configured, N_(T,2) is a time duration of N₂ symbols corresponding to PUSCH preparation time for PUSCH processing capability 1, N_(TA,max) is a maximum timing adjustment value that can be provided by the TA command field in the RAR.

Hereinafter, contention resolution will be described in more detail.

In response to an Msg3 PUSCH transmission when a UE has not been provided with a C-RNTI, the UE attempts to detect a PDCCH with a corresponding TC-RNTI scheduling a PDSCH that includes a UE contention resolution identity. In response to the PDSCH reception with the UE contention resolution identity, the UE transmits HARQ-ACK information in a PUCCH. A minimum time between the last symbol of the PDSCH reception and the first symbol of the corresponding HARQ-ACK transmission is equal to N_(T,1)+0.5 msec. N_(T,1) is a time duration of N1 symbols corresponding to a PDSCH reception time for PDSCH processing capability 1 when additional PDSCH DM-RS is configured.

FIG. 9 illustrates a frame structure applicable in NR.

Referring to FIG. 9 , a frame may consist of 10 milliseconds (ms) and may include 10 subframes of 1 ms.

A subframe may include one or a plurality of slots according to subcarrier spacing.

Table 8 below shows subcarrier spacing configuration μ.

TABLE 8 μ Δf = 2^(μ) · 15 [kHz] CP(Cyclic Prefix) 0 15 Normal 1 30 Normal 2 60 Normal, Extended 3 120 Normal 4 240 Normal

Table 9 below shows the number of slots in a frame (N^(frameμ) _(slot)), the number of slots in a subframe (N^(subframeμ) _(slot)), and the number of symbols in a slot (N^(slot) _(symb)) according to the subcarrier spacing configuration μ.

TABLE 9 μ N_(symb) ^(slot) N_(slot) ^(frame,μ) N_(slot) ^(subframe,μ) 0 14 10 1 1 14 20 2 2 14 40 4 3 14 80 8 4 14 160 16

FIG. 9 shows μ=0, 1, and 2. A physical downlink control channel (PDCCH) may include one or more control channel elements (CCEs) as shown in Table 80 below.

TABLE 10 Aggregation level Number of CCEs 1 1 2 2 4 4 8 8 16 16

In other words, the PDCCH may be transmitted through a resource including 1, 2, 4, 8 or 16 CCEs. Here, the CCE includes six resource element groups (REGs), and one REG includes one resource block in the frequency domain and one orthogonal frequency division multiplexing (OFDM) symbol in the time domain. The following technologies/characteristics may be applied to NR.

<Self-Contained Subframe Structure>

FIG. 10 illustrates an example of a frame structure for the new radio access technology (new RAT).

In NR, as a purpose for minimizing latency, as shown in FIG. 10 , a structure having a control channel and a data channel being processed with Time Division Multiplexing (TDM), within one TTI, may be considered as one type of frame structure.

In FIG. 10 , an area marked with slanted lines represents a downlink control area, and an area marked in black represents an uplink control area. An area marked in black may be used for downlink (DL) data transmission or may be used for uplink (UL) data transmission. The characteristic of such structure is that, since downlink (DL) transmission and uplink (UL) transmission are carried out sequentially, DL data is sent out (or transmitted) from a subframe, and UL Acknowledgement/Not-acknowledgement (ACK/NACK) may also be received in the subframe. As a result, time needed until data retransmission, when a data transmission error occurs, may be reduced, and, accordingly, latency in the final data transfer (or delivery) may be minimized

In the above-described data and control TDMed subframe structure, a time gap is needed for a transition process (or shifting process) from a transmission mode to a reception mode of the base station and UE, or a transition process (or shifting process) from a reception mode to a transmission mode of the base station and UE. For this, in a self-contained subframe structure, some of the OFDM symbols of a time point where a transition from DL to UL occurs may be configured as a guard period (GP).

FIG. 11 shows examples of 5G usage scenarios to which the technical features of the present specification can be applied. The 5G usage scenarios shown in FIG. 11 are only exemplary, and the technical features of the present specification can be applied to other 5G usage scenarios which are not shown in FIG. 11 .

Referring to FIG. 11 , the three main requirements areas of 5G include (1) enhanced mobile broadband (eMBB) domain, (2) massive machine type communication (mMTC) area, and (3) ultra-reliable and low latency communications (URLLC) area. Some use cases may require multiple areas for optimization and, other use cases may only focus on only one key performance indicator (KPI). 5G is to support these various use cases in a flexible and reliable way.

eMBB focuses on across-the-board enhancements to the data rate, latency, user density, capacity and coverage of mobile broadband access. The eMBB aims ˜10 Gbps of throughput. eMBB far surpasses basic mobile Internet access and covers rich interactive work and media and entertainment applications in cloud and/or augmented reality. Data is one of the key drivers of 5G and may not be able to see dedicated voice services for the first time in the 5G era. In 5G, the voice is expected to be processed as an application simply using the data connection provided by the communication system. The main reason for the increased volume of traffic is an increase in the size of the content and an increase in the number of applications requiring high data rates. Streaming services (audio and video), interactive video and mobile Internet connectivity will become more common as more devices connect to the Internet. Many of these applications require always-on connectivity to push real-time information and notifications to the user. Cloud storage and applications are growing rapidly in mobile communication platforms, which can be applied to both work and entertainment. Cloud storage is a special use case that drives growth of uplink data rate. 5G is also used for remote tasks on the cloud and requires much lower end-to-end delay to maintain a good user experience when the tactile interface is used. In entertainment, for example, cloud games and video streaming are another key factor that increases the demand for mobile broadband capabilities. Entertainment is essential in smartphones and tablets anywhere, including high mobility environments such as trains, cars and airplanes. Another use case is augmented reality and information retrieval for entertainment. Here, augmented reality requires very low latency and instantaneous data amount.

mMTC is designed to enable communication between devices that are low-cost, massive in number and battery-driven, intended to support applications such as smart metering, logistics, and field and body sensors. mMTC aims ˜10 years on battery and/or ˜1 million devices/km². mMTC allows seamless integration of embedded sensors in all areas and is one of the most widely used 5G applications. Potentially by 2020, IoT devices are expected to reach 20.4 billion. Industrial IoT is one of the areas where 5G plays a key role in enabling smart cities, asset tracking, smart utilities, agriculture and security infrastructures.

URLLC will make it possible for devices and machines to communicate with ultra-reliability, very low latency and high availability, making it ideal for vehicular communication, industrial control, factory automation, remote surgery, smart grids and public safety applications. URLLC aims ˜1 ms of latency. URLLC includes new services that will change the industry through links with ultra-reliability/low latency, such as remote control of key infrastructure and self-driving vehicles. The level of reliability and latency is essential for smart grid control, industrial automation, robotics, drone control and coordination.

Next, a plurality of use cases included in the triangle of FIG. 11 will be described in more detail.

5G can complement fiber-to-the-home (FTTH) and cable-based broadband (or DOCSIS) as a means of delivering streams rated from hundreds of megabits per second to gigabits per second. This high speed can be required to deliver TVs with resolutions of 4K or more (6K, 8K and above) as well as virtual reality (VR) and augmented reality (AR). VR and AR applications include mostly immersive sporting events. Certain applications may require special network settings. For example, in the case of a VR game, a game company may need to integrate a core server with an edge network server of a network operator to minimize delay.

Automotive is expected to become an important new driver for 5G, with many use cases for mobile communications to vehicles. For example, entertainment for passengers demands high capacity and high mobile broadband at the same time. This is because future users will continue to expect high-quality connections regardless of their location and speed. Another use case in the automotive sector is an augmented reality dashboard. The driver can identify an object in the dark on top of what is being viewed through the front window through the augmented reality dashboard. The augmented reality dashboard displays information that will inform the driver about the object's distance and movement. In the future, the wireless module enables communication between vehicles, information exchange between the vehicle and the supporting infrastructure, and information exchange between the vehicle and other connected devices (e.g., devices accompanied by a pedestrian). The safety system allows the driver to guide the alternative course of action so that he can drive more safely, thereby reducing the risk of accidents. The next step will be a remotely controlled vehicle or self-driving vehicle. This requires a very reliable and very fast communication between different self-driving vehicles and between vehicles and infrastructure. In the future, a self-driving vehicle will perform all driving activities, and the driver will focus only on traffic that the vehicle itself cannot identify. The technical requirements of self-driving vehicles require ultra-low latency and high-speed reliability to increase traffic safety to a level not achievable by humans.

Smart cities and smart homes, which are referred to as smart societies, will be embedded in high density wireless sensor networks. The distributed network of intelligent sensors will identify conditions for cost and energy-efficient maintenance of a city or house. A similar setting can be performed for each home. Temperature sensors, windows and heating controllers, burglar alarms and appliances are all wirelessly connected. Many of these sensors typically require low data rate, low power and low cost. However, for example, real-time HD video may be required for certain types of devices for monitoring.

The consumption and distribution of energy, including heat or gas, is highly dispersed, requiring automated control of distributed sensor networks. The smart grid interconnects these sensors using digital information and communication technologies to collect and act on information. This information can include supplier and consumer behavior, allowing the smart grid to improve the distribution of fuel, such as electricity, in terms of efficiency, reliability, economy, production sustainability, and automated methods. The smart grid can be viewed as another sensor network with low latency.

The health sector has many applications that can benefit from mobile communications. Communication systems can support telemedicine to provide clinical care in remote locations. This can help to reduce barriers to distance and improve access to health services that are not continuously available in distant rural areas. It is also used to save lives in critical care and emergency situations. Mobile communication based wireless sensor networks can provide remote monitoring and sensors for parameters such as heart rate and blood pressure.

Wireless and mobile communications are becoming increasingly important in industrial applications. Wiring costs are high for installation and maintenance. Thus, the possibility of replacing a cable with a wireless link that can be reconfigured is an attractive opportunity in many industries. However, achieving this requires that wireless connections operate with similar delay, reliability, and capacity as cables and that their management is simplified. Low latency and very low error probabilities are new requirements that need to be connected to 5G.

Logistics and freight tracking are important use cases of mobile communications that enable tracking of inventory and packages anywhere using location-based information systems. Use cases of logistics and freight tracking typically require low data rates, but require a large range and reliable location information.

FIG. 12 schematically illustrates an example of integrated access and backhaul links.

An example of a network having such integrated access and backhaul links is shown in FIG. 12 . Here, a relay node (rTRP) can multiplex access and backhaul links in time, frequency or space (e.g., beam based operation).

Operations of different links may be at the same frequency or different frequencies (which may also be referred to as “in-band” and “out-band” relays). Although efficient support of the out-band relay is important in some NR deployment scenarios, it is very important to understand in-band operation requirements that mean a close interaction with an access link operating at the same frequency in order to accept duplex constraint and prevent/mitigate interference.

In addition, operation of an NR system in mmWave spectrum can present some unique challenges including experiencing serious short-term blocking that may not be easily mitigated by a current RRC based handover mechanism due to a larger time scale necessary to complete a procedure than short-term blocking.

To overcome short-term blocking in the mmWave system, a fast RAN based mechanism (which does not necessarily require intervention of a core network) for switching between rTRPs.

Necessity for mitigating short-term blocking for NR operation in the mmWave spectrum along with requirement for easier deployment of a self-backhauled NR cell may cause necessity of development of an integrated framework that enables rapid switching of access and backhaul links.

In addition, over-the-air (OTA) coordination between rTRPs can be regarded as mitigation of interference and support of end-to-end route selection and optimization.

The following requirements and aspects may need to be solved by integrated access and backhaul (IAB) for NR.

-   -   Efficient and flexible operation for in-band and out-band relays         in indoor and outdoor scenarios     -   Multiple hops and redundant connection     -   End-to-end route selection and optimization     -   Support of backhaul link with high spectrum efficiency     -   Legacy NR UE support

Legacy new RAT was designed to support half-duplex devices. Further, half-duplex of an IAB scenario deserves to be supported and to become an object. In addition, a full-duplex IAB device can be researched.

In the IAB scenario, a donor gNB (DgNB) needs to schedule all links between related relay nodes (RNs) and UEs unless each RN has scheduling capability. In other words, the DgNB can collect traffic information in all related RNs, determine schedules with respect to all links and then notify each RN of schedule information.

FIG. 13 schematically illustrates an example of a link between a DgNB, an RN, and a UE.

According to FIG. 13 , for example, a link between DgNB and UE1 is an access link (access link), a link between RN1 and UE2 is also an access link, and a link between RN2 and UE3 may also mean an access link.

Similarly, according to FIG. 13 , for example, a link between DgNB and RN1 and a link between RN1 and RN2 may mean a backhaul link.

For example, backhaul and access links can be configured, and in this case, the DgNB can receive scheduling requests of UE 2 and UE 3 as well as a scheduling request of UE 1. Then, the DgNB can determine scheduling of two backhaul links and three access links and signal the scheduling result. Accordingly, this centralized scheduling includes delayed scheduling and waiting time problems.

On the other hand, distributed scheduling can be performed if each RN has scheduling capability. Then, immediate scheduling can be performed for an uplink scheduling request of a UE and backhaul/access links can be used more flexibly in response to surrounding traffic conditions.

FIG. 14 schematically shows an example of a backhaul link and an access link.

As shown in FIG. 14 , a link between a donor node and an IAB node or a link between IAB nodes is called a backhaul link. On the other hand, the link between the donor node and the UE or the link between the IAB node and the UE is called an access link. That is, a link between an MT and a parent DU or a link between a DU and a child MT may be referred to as a backhaul link, and a link between the DU and the UE may be referred to as an access link.

FIG. 15 schematically shows an example of a parent link and a child link.

As shown in FIG. 15 , the link between the IAB node and the parent node is called a parent link, and the link between the IAB node and the child node/UE is called a child link. That is, the link between the MT and the parent DU is called a parent link, and the link between the DU and the child MT/UE is called a child link.

However, depending on the interpretation or perspective, the link between the IAB node and the parent node is called a backhaul link, and the link between the IAB node and the child node/UE is also called an access link.

Hereinafter, the proposal of the present specification will be described.

The IAB node may receive a slot format configuration for communication with a parent node and a slot format configuration for communication with a child node/access UE.

As described above, the IAB node is configured with MT and DU, resource configuration for the MT to communicate with the parent node(s) is called MT configuration, and resource configuration for the DU to communicate with the child node(s) and the access UE(s) is referred to as a DU configuration.

More specifically, MT configuration may indicate link direction information for a parent link between the parent node and itself for the IAB node to communicate with the parent node. In addition, the DU configuration may indicate link direction and link availability information for a child link between the child node/access UE and itself for the IAB node to communicate with the child node and the access UE.

Considering the characteristic of sharing resources in the TDM method between the MT and the DU in the IAB node, the present specification proposes a characteristic that such link availability configuration should have in detail. Also, a method for determining link availability between an MT and a DU based on a link availability configuration is proposed.

Additional advantages, objects, and features of the present specification will be set forth in part in the description that follows, and will become apparent to those skilled in the art upon reviewing the following, or may be learned, in part, from the practice of the present specification. The objects and other advantages of the present specification may be realized and attained by means of the appended drawings as well as the claims and structures particularly pointed out in the claims.

The terms used in this specification may be as follows.

-   -   IAB node (IAB-node): a RAN node that supports radio access to         the terminal(s) and supports wireless backhaul of access         traffic.     -   IAB donor (IAB-donor): a RAN node that provides the UE's         interface to the core network and wireless backhaul function to         the IAB node(s).

Hereinafter, each abbreviation may correspond to an abbreviation of the following terms.

-   -   IAB: Integrated Access and Backhaul     -   CSI-RS: Channel State Information Reference Signal     -   DgNB: Donor gNB     -   AC: Access     -   BH: Backhaul     -   DU: Distributed Unit     -   MT: Mobile terminal     -   CU: Centralized Unit     -   IAB-MT: IAB mobile terminal     -   NGC: Next-Generation Core network     -   SA: Stand-alone     -   NSA: non-stand-alone     -   EPC: Evolved Packet Core

The configuration, operation, and other features of the present specification may be understood by the embodiments of the present specification described with reference to the accompanying drawings.

The content of the present specification is described assuming an in-band environment, but may be applied in an out-band environment. In addition, the content of the present specification is described in consideration of the environment in which the donor gNB (DgNB), the relay node (RN), and the UE perform a half-duplex operation, but it may also be applied in an environment in which a donor gNB (DgNB), a relay node (RN), and/or a UE performs a full-duplex operation.

In this specification, for convenience of description, when RN1 and RN2 exist, when RN1 is connected to RN2 by a backhaul link and relays data transmitted/received to RN2, RN1 is called the parent node of RN2 and RN2 is referred to as a child node RN of RN1.

The discovery signal referred to in this specification is a signal transmitted by the IAB node, it means a signal transmitted to enable other IAB nodes or UEs to discover the IAB itself.

Such a discovery signal may have the form of an SSB, a form of a CSI-RS of the NR specification or a form of a signal introduced into another existing NR. Or it may be a newly designed signal.

The content of the present specification mainly describes the content of the IAB node discovering other IAB nodes, but may also be applied when the UE discovers the IAB nodes.

On the other hand, from the IAB node MT point of view, the time domain resource (s) of the following type (s) may be indicated for the parent link.

-   -   Downlink time resources;     -   Uplink time resources;     -   Flexible time resources.

From an IAB node DU perspective, a child link may have time domain resource(s) of the following type(s).

-   -   Downlink time resource;     -   Uplink time resource;     -   Flexible time resources;     -   Unavailable time resource(s) (resource(s) not used for         communication on DU child link(s)).

Downlink, uplink, flexible time resource type(s) of the DU child link may belong to one of the following two categories.

-   -   Hard: this time resource is always available for DU child links;     -   Soft: The availability of a corresponding time resource for a DU         child link may be explicitly and/or implicitly controlled by the         parent node.

From the IAB node DU point of view, the child link has four types of time resources: downlink (DL), uplink (UL), flexible (F) and not available (NA). Here, the not available resource may mean that the resource is not used for communication on the DU child link(s).

Each of the downlink, uplink and flexible time resources of the DU child link may be a hard or soft resource. As described above, the hard resource may mean that communication is always possible in the DU child link. However, in the case of soft resources, communication availability in the DU child link may be explicitly and/or implicitly controlled by the parent node.

In such a situation, the configuration on the link direction (DL/UL/F/NA) and link availability (hard/soft) of the time resource for the DU child link may be named DU configuration.

This configuration can be used for effective multiplexing and interference processing among IAB node(s). For example, this configuration can be used to indicate which link is valid for the time resource between the parent link and the child link.

In addition, configuring only a subset of the child node(s), since it can utilize time resources for DU operation, it can be used to adjust interference among the child node(s).

Considering this aspect, the DU configuration may be more effective when the DU configuration is semi-static and can be configured specifically for the IAB node.

On the other hand, similar to the SFI configuration for the access link, the IAB node MT may have three types of time resources for the parent link: downlink (DL), uplink (UL) and flexible (F).

FIG. 16 schematically shows a configuration between nodes.

As in {circle around (1)} of FIG. 16 , the IAB node receives MT configuration that informs the link direction information for the parent link between the parent node and itself for communication with the parent node. In addition, as in {circle around (2)} of FIG. 16 , it receives a DU configuration that informs the link direction and link use availability information that can be used for communication to its own child link.

FIG. 17 schematically shows an example in which the MT and DU of the IAB node are configured with a plurality of CCs.

According to FIG. 17 , the MT and DU of the IAB node may be configured with a plurality of CC (component carrier). In this case, different CCs may operate in the same or different frequency domains or use the same or different panels. For example, as shown in FIG. 17 , each of the MT and the DU in the IAB node may have three CCs. In the drawing, three CCs existing in the MT are called MT-CC1, MT-CC2, and MT-CC3, respectively. In the case of DU, CC is replaced with a cell and is called DU-Cell1, DU-Cell2, and DU-Cell3.

In this case, between the specific CC of the MT and the specific cell of the DU, one of TDM, SDM/FDM, and FD multiplexing scheme may be applied. For example, when a specific MT-CC and a DU-cell are located in different inter-band frequency domains, FD may be applied between the corresponding MT-CC and the DU-cell. On the other hand, the TDM scheme may be applied between the MT-CC and the DU-CC located in the same frequency domain. FIG. 17 , MT-CC1, MT-CC2, DU-cell1, DU-cell2 have f1 as a center frequency, and MT-CC3 and DU-cell3 have f2 as a center frequency, f1 and f2 may be located within an inter-band of each other. In this case, in the position of MT-CC1 (or the position of MT-CC2), it operates by TDM with DU-cell 1 and DU-cell 2, but may operate in FD with DU-cell 3. On the other hand, from the standpoint of MT-CC3, it operates in FD with DU-cell 1 and DU-cell 2, but can operate in TDM with DU-cell 3.

On the other hand, another multiplexing scheme between MT and DU may be applied even within the same CC. For example, a plurality of parts may exist in the MT-CC and/or the DU-cell. Such a part may refer to, for example, an antenna having the same center frequency but a different physical location or a link transmitted through different panels.

Or, for example, the center frequency may mean a link transmitted through the same but different BWP. In this case, for example, when two parts exist in DU-cell 1, a multiplexing type operating with a specific MT-CC or a specific part within a specific MT-CC may be different for each part. The content of the following specification describes a case in which the multiplexing type applied to each pair of the MT's CC and the DU's cell may be different, but the content of the specification can be extended and applied even when MT and DU are divided into a plurality of parts and the multiplexing type applied to each pair of CC and part of MT and cell and part of DU may be different.

On the other hand, it may be considered that one IAB node is connected to two or a plurality of parent nodes. In this case, the IAB MT may be connected to two parent DUs using a dual-connectivity scheme.

The IAB node may have redundant route(s) to the IAB donor CU. For IAB node(s) operating in SA mode, NR DC can be used to enable path redundancy in BH by allowing IAB-MT to have BH RLC channel(s) simultaneously with two parent nodes.

A parent node may have to connect to the same IAB donor CU-CP that controls the establishment and release of redundant route(s) through two parent nodes.

A parent node can acquire the roles of a master node and a secondary node of the IAB-MT together with the IAB donor CU. The NR DC framework (e.g. MCG/SCG-related procedures) may be used to configure a dual radio link with the parent node(s).

Hereinafter, for a better understanding of the examples of the present specification, the disclosure of the present specification will be described with reference to the drawings. The following drawings were created to explain a specific example of the present specification. Since the names of specific devices described in the drawings or the names of specific signals/messages/fields are presented by way of example, the technical features of the present specification are not limited to the specific names used in the following drawings.

FIG. 18 is a flowchart of a method of transmitting and receiving information about a guard symbol, according to another embodiment of the present specification.

According to FIG. 18 , a node may transmit information about a desired guard symbol to a parent node (S1810).

As will be described later, ‘information on the desired guard symbol’, which is information about a guard symbol that a node transmits to a parent node, may have the same/similar form as ‘information on the guard symbols provided’, which is information about a guard symbol that a node to be described later receives from a parent node, here, ‘information on the provided guard symbol’ may correspond to information on a guard symbol (to be applied to a node), which will be described later.

That is, as described above, an embodiment of the table(s) to be described later may be applied to the desired guard symbol information, and a more specific embodiment thereof will be described later.

The node may receive information about the guard symbol provided from the parent node (S1820). Since a more specific embodiment will be described later, repeated description of overlapping content will be omitted for convenience of description.

In addition, the above-described ‘information on the desired guard symbol’ and/or ‘information on the provided guard symbol’ may be transmitted as MAC CE (and/or RRC)

On the other hand, an embodiment in which a node transmits information about a desired guard symbol to a parent node and an embodiment in which a node receives information about a guard symbol provided from a parent node may be implemented independently or together.

Hereinafter, embodiments of the present specification will be described in more detail.

A. Link Availability Determination

Information on link availability can inform the MT, inform the DU, or inform each of the MT and the DU of the IAB node.

When the link availability information is configured to the DU, the link availability information may include all or part of the following types.

-   -   Hard (H): The corresponding time resource is always available         for the DU child link.     -   Soft (S): The availability of the corresponding time resource         for the DU child link is explicitly and/or implicitly controlled         by the parent node.     -   Not available (NA): Resources not to be used for communication         on the DU child links.

When the link availability information is configured to the MT, each link availability type may mean the following.

-   -   Hard (H): The corresponding time resource is always available         for the MT parent link.     -   Soft (S): The availability of the corresponding time resource         for the MT parent link is explicitly and/or implicitly         controlled by the parent node.     -   Not available (NA): Resources not to be used for communication         on the MT parent link.

When the link availability information is configured to the IAB DU, the link availability type of the IAB DU may be informed in units of OFDM symbols/slots. Based on this, the IAB node may determine a time resource that can be used for the operation of the IAB MT. Conversely, when the link availability information is configured to the IAB MT, the link availability type of the IAB MT may be informed in units of OFDM symbols/slots. Based on this, the IAB node may determine a time resource that can be used for the operation of the IAB DU.

A.1. Timing Criteria to Configure Link Availability

When configuring link availability information to the IAB DU (or to the MT), the reference of timing for configuring link availability may be as follows. When the link availability information is configured to the IAB MT, the DU may be interpreted as being replaced with the MT in the following content.

(a) It is possible to configure time resource information that can be used by the DU based on the DL timing of the DU. For example, when OFDM symbols #4 to #7 are available for DU, based on the DL timing of the DU, the time domain in which OFDM symbols #4 to #7 are located becomes a time resource usable by the DU.

(b) It is possible to configure time resource information that can be used by the DU based on the UL timing of the DU. For example, when OFDM symbols #4 to #7 are available for DU, based on the UL timing of the DU, the time domain in which OFDM symbols #4 to #7 are located becomes a time resource usable by the DU.

(c) It is possible to configure time resource information that can be used by the DU based on a timing that matches the link direction configuration of the DU. For example, when OFDM symbols #4 to #7 are assumed to be available for DU, OFDM symbols #4 and #5 are downlink resources, and OFDM symbols #6 and #7 are uplink resources, time resources corresponding to OFDM symbols #4 and #5 based on DL timing and time resources corresponding to OFDM symbols #6 and #7 based on UL timing are time resources usable by DU.

(d) It is possible to configure time resource information that can be used by the DU based on the DL timing of the MT. For example, when OFDM symbols #4 to #7 are available for DU, based on the DL timing of the MT, the time domain in which OFDM symbols #4 to #7 are located becomes a time resource usable by the DU.

(e) It is possible to configure time resource information that can be used by the DU based on the UL timing of the MT. For example, when OFDM symbols #4 to #7 are available for DU, based on the UL timing of the MT, the time domain in which OFDM symbols #4 to #7 are located becomes a time resource usable by the DU.

(f) It is possible to configure the time resource information that the DU can use based on the timing suitable for the link direction configuration of the MT. For example, when OFDM symbols #4 to #7 are assumed to be available for DU, OFDM symbols #4 and #5 are MT downlink resources, and OFDM symbols #6 and #7 are MT uplink resources, time resources corresponding to OFDM symbols #4 and #5 based on MT DL timing and time resources corresponding to OFDM symbols #6 and #7 based on MT UL timing are time resources usable by DUs.

This link availability configuration may include a semi-static configuration and/or dynamic configuration.

On the other hand, for DU configuration, DU resource configuration (DL/UL/F) and H/S/NA indication on the DU resource configuration may be configured.

With respect to the time reference for the H/S/NA indication, two options can be considered. One option is that the H/S/NA indication is applied with respect to the DU resource configuration, and another option is that the H/S/NA indication is applied with respect to the MT resource configuration.

-   -   Option 1a: H/S/NA may be applied with respect to DU resource         configuration (D/U/F) slot timing without considering MT         resource configuration or timing.     -   Option 1b: H/S/NA may be applied with respect to MT resource         configuration (D/U/F) slot timing.

In option 1a, H/S/NA indication is applied with respect to the DU resource configuration, the resource availability of the MT resource may be determined based on the H/S/NA indication.

Due to the propagation delay between the MT and the parent DU, a timing gap may occur between the DU and the MT slot boundary. In general, the MT DL slot boundary may be located after the DU DL slot boundary, and the MT UL slot boundary may be located before the DU UL slot boundary (However, the present technology does not exclude the case where the MT DL slot boundary is located before the DU DL slot boundary and the MT UL slot boundary is behind the DU UL slot boundary). Therefore, in order to obtain MT resource availability in the H/S/NA indication, the timing gap may have to be reflected.

CU may determine and configure the RRC configuration for each child MT, such as semi-static data scheduling or signal/measurement related configuration(s). Accordingly, the CU needs to know the actual resource availability information of the child MT(s), and the timing gap information for each child node may have to be delivered to the CU.

On the other hand, in option 1b, H/S/NA indication may be applied in relation to MT resource configuration. The resource availability of the DU resource is obtained from the H/S/NA indication, and the timing gap between the DU and the MT slot boundary may be reflected similarly to the first option.

For each DU(s), the CU may determine and configure available resource(s) and semi-static data/signal transmission resources for the child link in consideration of interference among the DU(s). For this operation, the CU needs to know the actual resource availability information for each DU(s). Therefore, the CU may need to know the timing gap information between the DU and the MT as in option 1a.

In both options 1a and 1b, the CU may need to obtain timing gap information between the DU and the MT for each child node. Considering the multiplexing management aspect between DU(s), it may be more efficient to use consistent and absolute DU slot timing between CUs/DUs rather than MT slot timings that may change and are not aligned between DUs. Accordingly, H/S/NA indication may be applied in relation to DU resource configuration slot timing.

A.2. Method for Determining the Link Availability of the MT(DU) with the Link Availability Information of the DU(MT)

FIG. 19 schematically shows an example of timing adjustment.

When the IAB node receives the configuration (configure) for link availability with the DU, time resource information for performing the MT operation may be determined using the corresponding configuration. Conversely, if the IAB node receives the configuration for link availability with the MT, time resource information for performing the DU operation may be determined using the corresponding configuration.

At this time, even in the same IAB node, the DL timing of the DU, the UL timing of the DU, the DL timing of the MT, the UL timing of the MT may all be different. In the case of DL timing of DU, it is synchronized between nodes. The time at which the DL signal of the parent DU is received becomes the DL reception time of the MT. When the MT receives a TA (timing advance) value configured from the parent node, MT uplink transmission is performed by performing a timing advance by a value of ‘TA+TA_offset’ from the DL reception time.

Thereafter, in order to match the DL transmission timing between the IAB DUs, the timing advanced by ‘TA/2+TA_delta’ from the DL reception time of the IAB MT is configured as the DL timing of the DU. In this case, TA_delta is a value configured from the parent node. The UL timing of the DU is configured as fast as TA_offset in consideration of a DL/UL switching time with the DU DL timing, etc. An example of such a timing is shown in FIG. 19 . In this specification, TA_offset is also referred to as TAoffset. Also, TA_delta is sometimes denoted as Tdelta.

FIG. 20 is an example of a method for determining link availability of an MT based on link availability configured to a DU.

Referring to FIG. 20 , the IAB node receives the MT side configuration (MT configuration) and the DU side configuration (DU configuration) of the IAB node (S1610), the MT side link availability may be determined based on link availability information included in the DU side configuration (DU configuration) (S1620). The IAB node may perform an MT and/or DU side operation of the IAB node based on the link availability (S1630).

A method of determining the link availability of the MT with the link availability information configured to the DU may include all or part of the following.

(a) During the time resource configured to be used for the DU operation according to the criteria of A.1, the IAB node does not perform the MT operation. That is, it is determined that the resource in which the DU operation is hard and/or the soft resource indicated by the IA is a period in which the MT operation is not available.

(b) During the time resource configured not to be used for DU operation according to the criteria of A.1, the IAB node may perform MT operation. That is, it is determined that the resource in which the DU operation is NA and/or the soft resource indicated by the INA is a period in which the MT operation is available.

(c) When determining available resources and not available resources of the MT operation according to the criteria of (a), (b), etc., only a partial time domain of the MT OFDM symbol may be available (or not available). That is, a time domain in which an MT operation is available and a time domain in which an MT operation is not available may be mixed in the OFDM symbol. In this case, the OFDM symbol may operate as follows.

-   -   Alt 1. It may be determined that the MT operation is not         available in the entire OFDM symbol.

FIGS. 21 to 24 schematically show an example for determining the availability of a resource based on the relationship between the DU operation and the MT operation.

For example, OFDM symbols #4 to #7 based on the timing of the DU DL as shown in FIGS. 21 and 22 are NA resources of the DU, OFDM symbols #0 to #3, #8 to #13 may be configured as hard resources of the DU. At this time, the availability of the MT may be determined as follows.

-   -   In the case of DL of MT as shown in FIG. 21 , OFDM symbols #0 to         #1 and #7 to #13 configured to perform DU operation for the         entire time domain of the symbol may be determined as OFDM         symbols in which MT operation is not available. OFDM symbols #3         to #5 configured so that the DL operation of the DU is not         performed for the entire time domain of the symbol may be         determined as OFDM symbols in which the DL operation of the MT         is available. Meanwhile, since the timing of the MT and the         timing of the DU of the IAB node are not aligned with each         other, there is an OFDM symbol in which an area in which the DL         operation of the MT is available and an area in which it is not         available are mixed. In this example, OFDM symbols #2 and #6 are         such. In the case of these OFDM symbols, it can be determined as         an OFDM symbol in which the DL operation of the MT is not         available.     -   In the case of UL of MT as shown in FIG. 22 , OFDM symbols #0 to         #4 and #10 to #13 configured to perform DU operation for the         entire time domain of the symbol may be determined as OFDM         symbols in which MT operation is not available. OFDM symbols #6         to #8 configured so that the DU operation is not performed for         the entire time domain of the symbol may be determined as OFDM         symbols in which the UL operation of the MT is available. In the         case of OFDM symbols #5 and #9 in which an area in which the UL         operation of the MT is available and an area in which it is not         available are mixed, it may be determined as an OFDM symbol in         which the UL operation of the MT is not available.

Or, OFDM symbols #4 to #7 based on the timing of the DU UL as shown in FIGS. 23 and 24 are NA resources of the DU, OFDM symbols #0 to #3, #8 to #13 may be configured as hard resources of the DU. At this time, the availability of the MT may be determined as follows.

-   -   In the case of DL of MT as shown in FIG. 23 , OFDM symbols #0 to         #1 and #7 to #13 configured to perform DU operation for the         entire time domain of the symbol may be determined as OFDM         symbols in which MT operation is not available. OFDM symbols #3         to #5 configured so that the DL operation of the DU is not         performed for the entire time domain of the symbol may be         determined as OFDM symbols in which the DL operation of the MT         is available. Meanwhile, since the timing of the MT and the         timing of the DU of the IAB node are not aligned with each         other, there is an OFDM symbol in which an area in which the DL         operation of the MT is available and an area in which it is not         available are mixed. In this example, OFDM symbols #2 and #6 are         such. In the case of these OFDM symbols, it can be determined as         an OFDM symbol in which the DL operation of the MT is not         available.     -   In the case of UL of MT as shown in FIG. 24 , OFDM symbols #0 to         #4 and #10 to #13 configured to perform DU operation for the         entire time domain of the symbol may be determined as OFDM         symbols in which MT operation is not available. OFDM symbols #6         to #8 configured so that the DU operation is not performed for         the entire time domain of the symbol may be determined as OFDM         symbols in which the UL operation of the MT is available. In the         case of OFDM symbols #5 and #9 in which an area in which the UL         operation of the MT is available and an area in which it is not         available are mixed, it may be determined as an OFDM symbol in         which the UL operation of the MT is not available.

At this time, additionally, in the area where the link direction of the DU is DL, the availability of MT resources is determined based on the DL timing of the DU, in the area in which the link direction of the DU is UL, availability of MT resources may be determined based on the UL timing of the DU.

FIG. 25 is an example of a method for determining link availability of a DU based on link availability configured to the MT.

Referring to FIG. 21 , the IAB node receives the MT side configuration (MT configuration) and DU side configuration (DU configuration) of the IAB node (S2110), link availability on the DU side may be determined based on link availability information included in the MT side configuration (DU configuration) (S2120). The IAB node may perform an MT and/or DU side operation of the IAB node based on the link availability (S2130).

On the other hand, the method of determining the link availability of the DU with the link availability information configured to the MT may include all or part of the following.

(a) During the time resources configured to be used for MT operation according to the criteria of A.1, the IAB node does not perform the DU operation. That is, it is determined that the resource in which the MT operation is hard and/or the soft resource indicated by the IA is a section in which the DU operation is not available.

(b) During the time resource configured not to be used for MT operation according to the criteria of A.1, the IAB node may perform a DU operation. That is, it is determined that the resource in which the MT operation is NA and/or the soft resource indicated by the INA is a period in which the DU operation is available.

(c) When determining available resources and not available resources of the DU operation according to the criteria of (a), (b), etc., only a partial time domain of the DU OFDM symbol may be available (or not available). That is, a time domain in which the DU operation is available and a time domain in which the DU operation is not available may be mixed in the OFDM symbol. In this case, it may operate as follows in the corresponding OFDM symbol.

-   -   Alt 1. It may be determined that the DU operation is not         available in the entire OFDM symbol.     -   Alt 2. It can be determined that DU operation is available in         the entire OFDM symbol. At this time, in the OFDM symbol of the         MT that overlaps with the time domain in 1 which the OFDM symbol         is located (fully or partially), the MT determines that the OFDM         symbol is not available even if it is configured as a hard         resource.

FIGS. 26 to 29 schematically show another example for determining the availability of a resource based on the relationship between the DU operation and the MT operation.

For example, OFDM symbols #4 to #7 based on the timing of the MT DL as shown in FIGS. 26 and 27 are NA resources of the MT, OFDM symbols #0 to #3, #8 to #13 may be configured as hard resources of the MT. In this case, the availability of the DU may be determined as follows.

-   -   In the case of DL of DU as shown in FIG. 26 , OFDM symbols #0 to         #4 and #10 to #13 configured to perform MT operation for the         entire time domain of the symbol may be determined as OFDM         symbols in which DU operation is not available. OFDM symbols #6         to #8 configured so that the MT DL operation is not performed         for the entire time domain of the symbol may be determined as         OFDM symbols in which the DU DL operation is available. On the         other hand, since the “MT timing and DU timing” of the IAB node         are not aligned with each other, there is an OFDM symbol in         which a region in which the DL operation of the DU is available         and a region in which the DU operation is not available are         mixed. In this example, OFDM symbols #5 and #9 are such. In the         case of these OFDM symbols, 1) it may be determined as an OFDM         symbol in which the DL operation of the DU is not available,         or 2) it may be determined as an OFDM symbol in which the DL         operation of the DU is available.     -   In the case of UL of DU as shown in FIG. 27 , OFDM symbols #0 to         #4 and #10 to #13 configured to perform DU operation for the         entire time domain of the symbol may be determined as OFDM         symbols in which DU operation is not available. OFDM symbols #6         to #8 configured so that the MT operation is not performed for         the entire time domain of the symbol may be determined as OFDM         symbols in which the UL operation of the DU is available. In the         case of OFDM symbols #5 and #9 in which an area in which the UL         operation of the DU is available and an area in which the DU is         not available are mixed, 1) it may be determined as an OFDM         symbol in which the UL operation of the DU is not available,         or 2) it may be determined as an OFDM symbol in which the UL         operation of the DU is available.

Or, OFDM symbols #4 to #7 based on the timing of the MT UL as shown in FIGS. 28 and 29 are NA resources of the MT, OFDM symbols #0 to #3, #8 to #13 may be configured as hard resources of the MT. In this case, the availability of the DU may be determined as follows.

-   -   In the case of DL of DU as shown in FIG. 28 , OFDM symbols #0 to         #4 and #10 to #13 configured to perform MT operation for the         entire time domain of the symbol may be determined as OFDM         symbols in which DU operation is not available. OFDM symbols #6         to #8 configured so that the MT DL operation is not performed         for the entire time domain of the symbol may be determined as         OFDM symbols in which the DU DL operation is available. On the         other hand, since the timing of the MT of the IAB node and the         timing of the DU are not aligned with each other, there is an         OFDM symbol in which an area in which a DL operation of the DU         is available and an area in which it is not available are mixed.         In this example, OFDM symbols #5 and #9 are such. In the case of         these OFDM symbols, 1) it may be determined as an OFDM symbol in         which the DL operation of the DU is not available, or 2) it may         be determined as an OFDM symbol in which the DL operation of the         DU is available.     -   In the case of UL of DU as shown in FIG. 29 , OFDM symbols #0 to         #4 and #10 to #13 configured to perform DU operation for the         entire time domain of the symbol may be determined as OFDM         symbols in which DU operation is not available. OFDM symbols #6         to #8 configured so that the MT operation is not performed for         the entire time domain of the symbol may be determined as OFDM         symbols in which the UL operation of the DU is available. In the         case of OFDM symbols #5 and #9 in which an area in which the UL         operation of the DU is available and an area in which this is         not available are mixed, 1) it may be determined as an OFDM         symbol in which the UL operation of the DU is not available,         or 2) it may be determined as an OFDM symbol in which the UL         operation of the DU is available.

FIG. 30 is an example of a method for determining link availability based on link availability configured in each of the DU side and the MT side of the IAB node.

Referring to FIG. 30 , the IAB node receives the MT side configuration (MT configuration), the DU side configuration (DU configuration) and link determination criterion information of the IAB node (The configurations and information can be received individually or at least two or more together) (S3010), according to the link determination criterion information, based on the link availability information included in the MT side configuration (DU configuration) or the DU side configuration (DU configuration), link availability for at least one of the MT-side link and the DU-side link may be determined (S3020). Based on the determined link availability, the operation of the MT and/or DU side of the IAB node may be performed (S3030).

That is, in another method of the present specification, link availability information may be configured to the DU and the MT, respectively. In this case, it can operate as follows.

(a) When the IAB node determines the link availability of the MT and the DU, it may be configured whether the DU makes a decision based on the configured link availability configuration or the MT makes a decision based on the configured link availability configuration (that is, link determination criterion information may be provided). This configuration may be configured from a CU or a parent DU through SI, RRC, F1AP, or the like.

(b) The IAB node determines the link availability of the MT based on the link availability configuration configured by the MT, the link availability of the DU may be determined based on the link availability configuration configured by the DU. In this case, a collision may occur in the configured link availability. For example, it may be configured such that there is a time resource in which both the MT and the DU can operate. In this case, the priority between the MT operation and the DU operation may be determined according to a specific rule. This priority may be determined, for example, as follows. Characteristically, all or part of the following rules may be included.

-   -   MT may always have priority. That is, the IAB node may perform         the MT operation in a time interval configured so that time         resources in which both the MT and the DU can operate exist.     -   DU may always have priority. That is, the IAB node may perform         the DU operation in a time interval configured so that time         resources in which both the MT and the DU can operate exist.     -   In the resource configured to transmit and/or receive the         cell-specific signal/channel for the DU, the operation of the DU         may be performed.     -   Both MT and DU may be determined as soft resources in the time         period in which the collision occurs due to semi-static link         availability configuration. In such a resource, link         availability may be determined based on the method for         determining the availability of soft resources configured as         implicit/explicit afterwards.

A.3. Switching Time Between DU Operation and MT Operation

FIGS. 31 to 34 schematically illustrate an example of a gap time required for switching when performing switching between a DU operation and an MT operation.

When performing switching between the DU operation and the MT operation, there may be a gap time required for switching. At this time, if the configuration of the gap time is left as an IAB node implementation issue, transmitted data cannot be received properly due to differences in understanding of the gap time location between nodes, or data expected to be received may not be transmitted. Therefore, it is suggested to configure the gap time as follows.

(a) When switching between the DU operation and the MT operation, the DU operation has priority over the MT operation. Therefore, a gap time is always created in the MT resource.

-   -   When switching the operation from DU to MT, after the OFDM         symbol at the end of the DU operation, X OFDM symbols or Y msec         may be configured/assumed as a gap time.     -   When switching operation from MT to DU, X OFDM symbols or Y msec         before the start OFDM symbol of DU operation may be         configured/assumed as a gap time.

An example of such an operation is shown in FIG. 31 . In the figure, the DU operation should be performed up to OFDM symbol #3 of the DU, and the MT operation should be performed from OFDM symbol #3 of the MT. In this case, since the operation of the DU takes precedence, it can be assumed that OFDM symbol #4 of the DU, which is one symbol, after the DU operation is terminated, is the gap time. Conversely, the MT operation should be performed up to OFDM symbol #12 of the MT, and the DU operation should be performed from OFDM symbol #12 of the DU. In this case, since the DU operation has priority, OFDM symbol #11 of the DU, which is 1 symbol before the start of the DU operation, may be assumed as the gap time.

(b) When performing switching between the DU operation and the MT operation, the operation of the MT takes precedence over the operation of the DU. Therefore, a gap time is always created in the DU resource.

-   -   When switching operation from DU to MT, X OFDM symbols or Y msec         preceding the start OFDM symbol of MT operation may be         configured/assumed as the gap time.     -   When switching operation from MT to DU, after the OFDM symbol at         the end of the MT operation, X OFDM symbols or Y msec may be         configured/assumed as the gap time.

An example of such an operation is shown in FIG. 32 . In the figure, the DU operation should be performed up to OFDM symbol #3 of the DU, and the MT operation should be performed from OFDM symbol #3 of the MT. In this case, since the operation of the MT has priority, OFDM symbol #2 of the MT, which is one symbol before the operation of the MT starts, may be assumed as the gap time. Conversely, the MT operation should be performed up to OFDM symbol #12 of the MT, and the DU operation should be performed from OFDM symbol #12 of the DU. In this case, since the MT operation has priority, OFDM symbol #13 of the DU, which is one symbol after the MT operation is terminated, may be assumed as the gap time.

(c) When performing switching between the DU operation and the MT operation, the operation of the currently operating link takes precedence.

-   -   When switching the operation from—DU to MT, X OFDM symbols or Y         msec after the end of the DU operation start OFDM symbol may be         configured/assumed as the gap time.     -   When switching the operation from MT to DU, X OFDM symbols or Y         msec after the end OFDM symbol of the MT operation may be         configured/assumed as the gap time.

An example of such an operation is shown in FIG. 33 . In the figure, the DU operation should be performed up to OFDM symbol #3 of the DU, and the MT operation should be performed from OFDM symbol #3 of the MT. In this case, since the operation of the currently operating DU has priority, OFDM symbol #4 of the DU, which is one symbol after the DU operation is terminated, may be assumed as the gap time. Conversely, the MT operation should be performed up to OFDM symbol #12 of the MT, and the DU operation should be performed from OFDM symbol #12 of the DU. In this case, the currently operating MT operation has priority, and OFDM symbol #13 of the DU, which is 1 symbol after the MT operation is terminated, may be assumed as the gap time.

(d) When performing switching between the DU operation and the MT operation, the operation of the link to be performed after switching takes precedence.

-   -   When switching the operation from the DU to the MT, X OFDM         symbols or Y msec before the start OFDM symbol of MT operation         may be configured/assumed as the gap time.     -   When switching operation from MT to DU, X OFDM symbols or Y msec         before the start OFDM symbol of DU operation may be         configured/assumed as the gap time.

An example of such an operation is shown in FIG. 34 . In the figure, the DU operation should be performed up to OFDM symbol #3 of the DU, and the MT operation should be performed from OFDM symbol #3 of the MT. In this case, the operation of the MT to be operated after switching has priority, and OFDM symbol #2 of the MT, which is one symbol before the operation of the MT starts, may be assumed as the gap time. Conversely, the MT operation should be performed up to OFDM symbol #12 of the MT, and the DU operation should be performed from OFDM symbol #12 of the DU. In this case, the DU operation to be operated after switching has priority, and OFDM symbol #11 of the DU, which is 1 symbol before the start of the DU operation, may be assumed as the gap time.

(e) When performing switching between the DU operation and the MT operation, the IAB node may receive information on a priority operation among the MT operation and the DU operation from the CU or parent node through SI, RRC, F1AP, or the like. When the MT operation is configured to take precedence, the gap time is configured as in the method (b) above, when the DU operation is configured to be prioritized, the gap time may be configured as in the method (a) above.

If such a gap time exists in the MT resource, it can be assumed that the IAB node does not perform transmission/reception operations to the MT during the gap time. On the other hand, if the gap time exists in the DU resource, it can be assumed that the IAB node does not perform transmission/reception operations to the DU during the gap time. At this time, if this gap time overlaps a part in the OFDM symbol, it can be assumed that no transmission/reception operation is performed on the entire OFDM symbol.

A.4. Operation in Time Resource Between UL Resource and DL Resource of MT

FIGS. 35 and 36 schematically show an example of link availability.

When configuring link availability information based on the timing of MT, for example, as shown in FIG. 35 , OFDM symbols #0 to #3, #12 to #13 of MT are configured as available resources for MT operation, OFDM symbols #4 to #11 of the MT may be configured as resources not available for MT operation. At this time, the operation of the DU is unavailable in the time domain where the operation of the MT is available, it may be determined that the operation of the DU is available in a time domain in which the operation of the MT is not available.

At this time, as in FIG. 35 , the DU resource region corresponding to OFDM symbols #12 to #13 of the MT and the DU resource region corresponding to OFDM symbols #0 to #3 of the MT in the next slot become resources that are not available for DU operation. In this case, DU OFDM symbols #10, #11, #12 and DU OFDM symbols #1, #2, #3, #4, and #5 of the next slot become resources not available for DU operation. In this case, OFDM symbols #13 and #0 of the DU are gap regions due to UL to DL switching of the MT, and are resources on which MT operation is not performed. Accordingly, the DU operation may be performed in such an OFDM symbol. Therefore, in the present specification, it is proposed that the DU operation can be performed during the time between the UL end time and the DL start time of the MT.

On the other hand, when configuring (configure) link availability information based on the timing of the DU, for example, as shown in FIG. 36 , OFDM symbols #0 to #3 and #12 to #13 of the DU are configured as resources not available for DU operation, OFDM symbols #4 to #11 of the DU may be configured as available resources for DU operation. In this case, it may be determined that the operation of the MT is not available in a time domain in which the operation of the DU is available, and it may be determined that the MT operation is available in a time domain in which the DU operation is not available.

At this time, OFDM symbols #12 and #13 of the DU and OFDM symbols #0, #1, #2, and #3 of the next slot in FIG. 36 are resources on which the DU operation is not performed. However, OFDM symbols #13 and #0 of the DU are gap regions due to UL to DL switching of the MT, and are resources on which MT operation is not performed. Therefore, in the present specification, it is proposed that the DU operation can be performed regardless of the availability of the DU during the time between the UL end time and the DL start time of the MT.

A.5. Method of Determining Resource Availability

When the H/S/NA indication is configured as a DU and applied for the DU resource configuration related to the H/S/NA indication, the resource availability of the MT resource may be determined based on the H/S/NA indication.

FIG. 37 schematically shows an example of MT resource availability determination.

In FIG. 37 , DU symbols #0-#2 and #6-#9 may be configured as NAs, and symbols #3-#5 and #10-#13 may be configured as hard resources.

FIG. 37(a) schematically illustrates an example of a case where the MT downlink resource availability and the DU has a downlink resource direction.

When both MT and DU are in the downlink, MT symbols #2, #3, #9, #10 and #11 do not become available resources for MT operation because these resources are indicated as DU hard resources.

For MT symbols #1, #4, #8 and #12, since a part of the symbol resource is occupied for DU operation, these symbols cannot be used even for MT.

When the entire area of the MT symbol is indicated as NA for DU operation, the above symbols, such as MT symbols #0, #5, #6, #7, and #13, may be available for MT operation.

On the other hand, in this example described above, the soft resource is not configured. However, if the MT symbol resource is indicated as a soft+NA resource or a soft resource from a DU perspective, the MT symbol may be interpreted as a symbol whose availability is not determined.

FIGS. 37(b), (c), (d) shows the resource availability determination for other MT and DU resource direction cases.

MT downlink, MT uplink, DU downlink and DU uplink all have different slot timing, the amount of relative slot timing gap may depend on the resource direction of the MT and DU. Therefore, the availability of MT symbols depends on the resource direction of the MT and DU.

For example, the MT uplink and DU downlink cases in FIG. 37(c), MT symbols #2-#3 and #8-#10 are available for MT operation, the result is different from the MT downlink and DU downlink cases. This is because the MT uplink reception timing precedes the MT downlink transmission timing by the TA.

On the other hand, since it is necessary to know the actual resource availability information of the CU MT, timing gap information between DU and MT should be communicated to CU to obtain MT resource availability. Here, two methods of delivering the timing gap information to the CU may be considered.

1. Option A. Report Timing Gap Values

The relative timing gap between MT and DU is shown in Table 11. In the table, the values of the relative timing gap (GT, XY) are shown according to the MT and DU resource directions, where X and Y are the MT and DU resource directions, respectively.

In addition, the following contents can be assumed in the table.

-   -   TA is a timing gap between MT uplink TX timing and MT downlink         RX timing.     -   TAoffset is a timing gap between the DU uplink RX timing and the         DU downlink TX timing.     -   DU downlink TX timing is ahead of its MT downlink Rx timing by         TAd/2+Tdelta.

Then, since the MT timing can be obtained as ‘MT timing=DU timing+GT, XY’, the CU can acquire actual MT resource availability if it knows the value of GT, XY for each case. To this end, the MT may report GT, DD, GT, DU, GT, UD, and/or GT, UU values to the parent DU and/or CU.

Instead of delivering GT, XY for the four resource direction cases, the CU can calculate the timing gap value using TA, TAd, Tdelta, and TAoffset.

Regarding the TA value, it may be difficult to ensure that the parent DU knows the exact TA value applied at the MT side. Therefore, it may be necessary for the MT to feed back the correct value of the TA to the CU and the parent DU.

If the values of TAd and Tdelta are configured by RRC, these values may be known to the CU. However, when these values are configured by the MAC CE (control element), these values need to be reported to the CU from the parent node. Regarding TAoffset, if the CU and child DU(s) do not use the same TAoffset value, the TAoffset for each child DU(s) should also be reported to the CU.

When reporting the TA value applied by the MT to the CU and/or parent DU, this value may be an absolute TA value that is most recently updated and applied by the MT. It can be reported periodically or aperiodically. In the case of periodic reporting, the MT may be configured with a reporting period and resource location. Alternatively, the reportable resource area is configured periodically, but the actual report can be performed only when the TA value is changed over a certain range. If the TA value is reported aperiodically, when a request message from the parent DU comes, the report may be performed.

Table 11 below schematically illustrates an example of a relative timing gap between an MT and a DU.

TABLE 11 MT downlink MT uplink DU G_(T,DD) = TA_(d/2) + T_(delta) GT,UD = TA_(d/2) + T_(delta) − TA downlink DU G_(T,DU) = TA_(d/2) + T_(delta) + GT,UU = TA_(d/2) + T_(delta) − TA + uplink TA_(offset) TA_(offset)

2. Option B. Report the Number of Gap Symbols.

Instead of feeding back the value of the time gap, information about the number of gap symbols may be delivered to the CU. Based on the example of FIG. 37 described above, the number of gap symbols (GS, XY) is shown in Table 12. If necessary, this value may be determined by the IAB node itself in consideration of the timing interval between the MT and the DU and the MT/DU switching time.

In this option, the availability of MT resources can be obtained using this value(s) without accurate timing interval information.

In successive OFDM symbols #S1-#S2, DU is indicated as hard, and G_(S, X1Y1) and G_(S, X2Y2) may each assume that the number of gap symbols reflects the MT and DU resource directions in symbols #S1 and #S2, respectively. Then, symbols that cannot be used for MT operation can be interpreted as #S1+G_(S, X1Y1)-#S2+G_(S, X2Y2)+1.

On the other hand, when consecutive DU symbols #S3-#S4 are indicated by NA, symbols #S3+G_(S, X3Y3)+1-#S4+G_(S, X4Y4) are available for MT operation. For example, as shown in FIG. 37 , OFDM symbols #3-#5 are DU hard symbols. If both the MT and the DU are in the downlink during the time resource, MT symbols #3+G_(S, DD)-#5+G_(S, DD+)1=#1-#4 cannot be used in MT operation. Therefore, in option B, the CU can obtain the actual MT resource availability by obtaining the number of gap symbols for each resource direction case.

When the number of gap symbols is reported, it may be reported periodically or aperiodically. In the case of periodic reporting, the MT may receive a report period and resource location configured. Alternatively, the reportable resource area is periodically configured, but actual reporting can be performed only when there is a change in the gap symbol value. When the number of gap symbols is reported aperiodically, the report may be performed when a request message from a parent DU is received.

TABLE 12 MT downlink MT uplink DU downlink G_(S,DD) = −2 G_(S,UD) = 1 DU uplink G_(S,UD) = −2 G_(S,UU) = 1

The number of such gap symbols may be independently configured when switching from DU operation to MT operation and from MT operation to DU operation. That is, for example, when switching from DU operation to MT operation, the number of gap symbols required according to the resource direction combination of MT and DU may be determined and reported as described above. In addition, in the case of switching from MT operation to DU operation, the number of gap symbols required according to the combination of resource directions of MT and DU may be determined and reported as described above. If the above description is amplified, the operation can be performed as follows.

(a) When the number of gap symbols is independently configured when switching from DU operation to MT operation and when switching from MT operation to DU operation

When the number of gap symbols (G_(S)) has a positive number, it means that the MT operates as follows.

-   -   When the DU is switched from the MT operation to start the DU         operation from symbol #n, the MT does not use as many symbols as         |G_(S)| before symbol #n as the MT timing reference.     -   When the DU switches to the MT operation after performing the DU         operation up to symbol #n, the MT does not use as many symbols         as |G_(S)| after symbol #n as the MT timing reference.

When the number of gap symbols (G_(S)) has a negative number, it means that the MT operates as follows.

-   -   When the DU is switched from the MT operation to start the DU         operation from symbol #n, the MT may additionally use as many         |G_(S)| symbols after symbol #n−1 as the MT timing reference.     -   When the DU switches to the MT operation after performing the DU         operation up to symbol #n, the MT may additionally use as many         as |G_(S)| symbols before symbol #n+1 as the MT timing         reference.

In the above description, the operation when the number of gap symbols (G_(S)) has a positive number and a negative number may be interchanged.

In addition, the operations described above may operate independently and/or together. In other words, as described above, the embodiment of the present specification may be provided only when the number of gap symbols is positive, or the embodiment of the present specification may be provided only when the number of gap symbols is negative. In addition, the embodiment of the present specification may be provided for both the embodiment for the case where the number of gap symbols is positive and the embodiment for the case where the number of gap symbols is negative.

(b) The number of gap symbols is provided only for the case of switching from DU to MT, and is commonly applied when switching from DU operation to MT operation and when switching from MT operation to DU operation.

When the number of gap symbols (G_(S)) has a positive number, it means that the MT operates as follows.

-   -   When the DU is switched from the MT operation to start the DU         operation from symbol #n, the MT may additionally use as many         symbols as |G_(S)|−1 after symbol #n−1 as the MT timing         reference.     -   When the DU switches to the MT operation after performing the DU         operation up to symbol #n, the MT does not use as many symbols         as |G_(S)| after symbol #n as the MT timing reference.

When the number of gap symbols (G_(S)) has a negative number, it means that the MT operates as follows.

-   -   When the DU is switched from the MT operation to start the DU         operation from symbol #n, the MT does not use as many symbols as         |G_(S)|+1 before symbol #n as the MT timing reference.     -   When the DU switches to the MT operation after performing the DU         operation up to symbol #n, the MT may additionally use as many         symbols as |G_(S)| before symbol #n+1 as the MT timing         reference.

In addition, the operations described above may operate independently and/or together. In other words, as described above, the embodiment of the present specification may be provided only when the number of gap symbols is positive, or the embodiment of the present specification may be provided only when the number of gap symbols is negative. In addition, the embodiment of the present specification may be provided for both the embodiment for the case where the number of gap symbols is positive and the embodiment for the case where the number of gap symbols is negative.

(c) The number of gap symbols is provided only for the case of switching from MT to DU, and is commonly applied when switching from DU operation to MT operation and when switching from MT operation to DU operation.

When the number of gap symbols (G_(S)) has a positive number, it means that the MT operates as follows.

-   -   When the DU is switched from the MT operation to start the DU         operation from symbol #n, the MT does not use as many symbols as         |G_(S)| before symbol #n as the MT timing reference.     -   When the DU switches to the MT operation after performing the DU         operation up to symbol #n, the MT may additionally use as many         symbols as |G_(S)|−1 before symbol #n+1 as the MT timing         reference.

When the number of gap symbols (G_(S)) has a negative number, it means that the MT operates as follows.

-   -   When the DU is switched from the MT operation to start the DU         operation from symbol #n, the MT may additionally use as many         |G_(S)| symbols after symbol #n−1 as the MT timing reference.     -   When the DU switches to the MT operation after performing the DU         operation up to symbol #n, the MT does not use as many symbols         as |G_(S)|+1 after symbol #n as the MT timing reference.

In addition, the operations described above may operate independently and/or together. In other words, as described above, the embodiment of the present specification may be provided only when the number of gap symbols is positive, or the embodiment of the present specification may be provided only when the number of gap symbols is negative. In addition, the embodiment of the present specification may be provided for both the embodiment for the case where the number of gap symbols is positive and the embodiment for the case where the number of gap symbols is negative.

(d) Among the case of switching from DU operation to MT operation and the case of switching from MT operation to DU operation, the number of gap symbols is provided only when the number of gap symbols has a positive number, and is commonly applied to the case of switching from DU operation to MT operation and the case of switching from MT operation to DU operation.

When the number of gap symbols (G_(S)) for the case of switching from DU to MT is provided, it means that the MT operates as follows.

-   -   When the DU is switched from the MT operation to start the DU         operation from symbol #n, the MT may additionally use as many as         |G_(S)|−1 symbols after symbol #n−1 as the MT timing reference.     -   When the DU switches to the MT operation after performing the DU         operation up to symbol #n, the MT may not use as many as |G_(S)|         symbols after symbol #n as the MT timing reference.

If the number of gap symbols (G_(S)) for the case of switching from MT to DU is provided, it means that the MT operates as follows.

-   -   When the DU is switched in the MT operation to start the DU         operation from symbol #n, the MT does not use as many symbols as         |G_(S)| before symbol #n as the MT timing reference.     -   When the DU switches to the MT operation after performing the DU         operation up to symbol #n, the MT may additionally use as many         symbols as |G_(S)|−1 before symbol #n+1 as the MT timing         reference.

Meanwhile, in the previous description, the above-described embodiments have been described mainly using the term ‘gap’. However, the term ‘gap’ previously used may be used interchangeably with the term ‘guard’. Accordingly, in the embodiments to be described later (and/or in the aforementioned embodiments), the terms ‘gap’ and ‘guard’ will be used interchangeably.

<Feedback for Reporting DU/MT Gap>

As in option A or option B above, an operation in which the MT reports the timing gap value (or TA, TA_(d), T_(delta), and/or TA_(offset) value) or the number of gap symbols to the parent node will be referred to as ‘DU/MT gap reporting’. When the MT reports the DU/MT gap to the parent node, the parent node may transmit feedback for the report to the MT. Such feedback may be specifically as follows.

-   -   Alt 1. An indication indicating that the DU/CU has reflected the         DU/MT gap report information received from the child node may be         informed to the child node. That is, the MT may receive an         indication that the reported value has been applied from the         parent node. Upon receiving such feedback, the MT may assume         that its reported DU/MT gap report is applied.     -   Alt 2. The DU/CU may inform the corresponding child node of an         indication indicating whether the DU/MT gap report information         received from the child node is reflected. That is, the MT may         receive an indication of whether to apply the reported value         from the parent node. If this feedback indicates that the value         reported by the MT is applied, the MT may assume that the DU/MT         gap report reported by the MT is applied.     -   Alt 3. The DU/CU may inform the MT of the actual timing gap         value (or TA, TA_(d), T_(delta), and/or TA_(offset) values) or         the number of gap symbols (after receiving the DU/MT gap report         from the child node). That is, the MT may receive, from the         parent node, feedback for the number of gap symbols or timing         gap values (or TA, TA_(d), T_(delta), and/or TA_(offset) values)         actually applied by the parent node as a result of their report.         When the number of gap symbols actually applied by the DU/CU is         informed to the MT, the number of gap symbols reflected in all         cases described in option B may be informed.

Such feedback may be transmitted through MAC CE or RRC.

Additionally, the MT may assume that the number of gap symbols or the timing gap value (or TA, TA_(d), T_(delta), and/or TA_(offset) values) reported by the MT or fed back by the parent node at a specific time point after receiving such feedback is applied. This specific point in time may be determined as follows.

-   -   Alt a. After the MT receives the feedback from the parent node,         it can be applied after N symbols. In this case, the value of N         may be defined in the specification (pre-configured and/or         predefined) or may be configured by RRC, MAC CE, etc. from a         parent node. Characteristically, the value of N may be included         in the feedback and transmitted.     -   Alt b. After the MT receives the feedback from the parent node,         it may be applied starting from M slots (mini-slots). In this         case, the value of M may be defined in the specification         (pre-configured and/or predefined), or configured by RRC, MAC         CE, or the like from a parent node. Characteristically, the         value of N may be included in the feedback and transmitted.

In summary, in order for the CU to obtain actual MT resource availability, the MT may report a) a timing gap-related value of option A or b) the number of gap symbols of option B.

The method of notifying the timing gap-related information may be similarly applied to the case in which the H/S/NA indication is transmitted based on the timing of the MT resource configuration, thereby determining the availability of the actual DU resource.

When the H/S/NA indication is transmitted based on the timing of the MT resource configuration, it is possible to determine the resource availability of the DU symbol as follows.

-   -   If the entire time domain of the DU symbol is configured as a         hard resource: Determined as a DU hard resource     -   If all or part of the time domain of the DU symbol is configured         as an NA resource: Determined as a DU NA resource     -   If the entire time domain of the DU symbol is configured as soft         or a soft resource and hard resource are combined: Determined as         DU soft resource

At this time, when the H/S/NA indication is transmitted based on the timing of the MT resource configuration, it is possible to determine the resource availability of the MT symbol as follows.

-   -   If the MT symbol area is configured as a DU hard resource:         Determined as an unavailable resource for MT operation     -   If the MT symbol area is configured as a DU NA resource:         Determined as a resource available for MT operation     -   If the MT symbol area is configured as a DU soft resource:         Determined as a resource that is not determined whether MT         operation is possible

Meanwhile, in the previous description, the above-described embodiments have been described mainly using the term ‘gap’. However, the term ‘gap’ previously used may be used interchangeably with the term ‘guard’. Accordingly, in the embodiments to be described later (and/or in the aforementioned embodiments), the terms ‘gap’ and ‘guard’ will be used interchangeably.

In addition, in the previous description, between the example in which the MT transmits information about the number of guard symbols (and/or gap values) to the parent node and the example in which the parent node transmits information about the number of guard symbols (and/or gap values) to the MT (to be applied to the MT), a companionship relationship does not necessarily exist. That is, an embodiment in which the MT transmits information on the number of guard symbols (and/or gap values) to the parent node and an embodiment in which the parent node transmits information about the number (and/or gap value) of guard symbols (to be applied to the MT) to the MT may operate as a separate embodiment. Of course, as a natural example, an example, in which the parent node transmits information about the number (and/or gap value) of the guard symbols (to be applied to the MT) to the MT after the MT transmits information about the number of guard symbols (and/or gap values) to the parent node, corresponds to an example provided herein.

If the specification once again describes the examples described above, it may be as follows. Hereinafter, for convenience of understanding of the above-described examples, examples of the above-described examples with reference to the drawings will be described once again.

Hereinafter, for a better understanding of the examples of the present specification, the disclosure of the present specification will be described with reference to the drawings. The following drawings were created to explain a specific example of the present specification. Since the names of specific devices described in the drawings or the names of specific signals/messages/fields are presented by way of example, the technical features of the present specification are not limited to the specific names used in the following drawings.

FIG. 38 is a flowchart of a method for transmitting guard symbol information, according to an embodiment of the present specification.

Referring to FIG. 38 , the node may determine the guard symbol information (S3810).

Here, the guard symbol information may inform each of the number of guard symbols related to switching between a mobile terminal (MT) operation and a distributed unit (DU) operation desired by the node. In addition, the guard symbol may be an unused symbol based on a transition between the MT operation and the DU operation.

Specifically, the guard symbol information (in other words, information about the guard symbol) may be the same as the example of Table 12 described above. Here, if the example of Table 12 is more generalized to describe an example of the information on the guard symbol, it may be as shown in the table below.

TABLE 13 MT downlink MT uplink DU Information on the number Information on the number downlink of guard symbols 1 of guard symbols 2 DU Information on the number Information on the number uplink of guard symbols 3 of guard symbols 4

Here, as described above, the DU downlink may mean DU TX, and the DU uplink may mean DU RX. In addition, the MT downlink may mean MT RX, and the MT uplink may mean MT TX. As described above, since the number of guard symbols can be defined for a case of switching from DU operation to MT operation and a case of switching from MT operation to DU operation, respectively, an example of the information on the guard symbol described in the table above can be described again in the form below.

TABLE 14 MT to DU DL Tx UL Rx DL Rx Information on the number Information on the number of guard symbols 1 of guard symbols 2 UL Tx Information on the number Information on the number of guard symbols 3 of guard symbols 4 DU to MT DL Rx UL Tx DL Tx Information on the number Information on the number of guard symbols 5 of guard symbols 6 UL Rx Information on the number Information on the number of guard symbols 7 of guard symbols 8

In addition, if the above-described information on the guard symbol is expressed in another form, it can be defined again as the table below.

TABLE 15 Field for number of guard Switching scenario symbols in MAC CE IAB-MT operation to DL Rx to DL Tx number of guard symbols 1 IAB-DU operation (NmbGS₁) DL Rx to UL Rx number of guard symbols 2 (NmbGS₂) UL Tx to DL Tx number of guard symbols 3 (NmbGS₃) UL Tx to UL Rx number of guard symbols 4 (NmbGS₄) IAB-DU operation to DL Tx to DL Rx number of guard symbols 5 IAB-MT operation (NmbGS₅) DL Tx to UL Tx number of guard symbols 6 (NmbGS₆) UL Rx to DL Rx number of guard symbols 7 (NmbGS₇) UL Rx to UL Tx number of guard symbols 8 (NmbGS₈)

An example of the information on the guard symbol described above will be described again as follows. For example, the guard symbol information may include first information and second information.

Here, for example, the first information may be information about the number of guard symbols for the transition from the MT operation to the DU operation (For example, in Table 14, information 1 on the number of guard symbols, information 2 on the number of guard symbols, information 3 on the number of guard symbols, information 4 on the number of guard symbols; For example, in Table 15, number of guard symbols 1 (NmbGS1), number of guard symbols 2 (NmbGS2), number of guard symbols 3 (NmbGS3), number of guard symbols 4 (NmbGS4)).

Also, for example, the second information may be information about the number of guard symbols for the transition from the DU operation to the MT operation (For example, in Table 14, information on the number of guard symbols 5, information on the number of guard symbols 6, information on the number of guard symbols 7, information on the number of guard symbols 8; For example, in Table 15, number of guard symbols 5 (NmbGS5), number of guard symbols 6 (NmbGS6), number of guard symbols 7 (NmbGS7), number of guard symbols 8 (NmbGS8)).

As described above, for example, the MT operation is at least one of MT TX (transmission) and MT RX (reception), and the DU operation may include at least one of DU TX and DU RX.

Reorganizing the example described above, for example, the first information may inform at least one of information on the number of guard symbols for the transition from the MT RX to the DU TX, information on the number of guard symbols for the transition from the MT RX to the DU RX, information on the number of guard symbols for the transition from the MT TX to the DU TX, or information on the number of guard symbols for the transition from the MT TX to the DU RX.

Also, for example, the second information may indicate at least one of information on the number of guard symbols for the transition from the DU TX to the MT RX, information on the number of guard symbols for the transition from the DU TX to the MT TX, information on the number of guard symbols for the transition from the DU RX to the MT RX, or information on the number of guard symbols for the transition from the DU RX to the MT TX.

Meanwhile, as described above, information on the guard symbol may be based on MAC CE.

The node may apply the information on the guard symbol (S3420).

Here, for example, when the node receives information about the guard symbol, the number of guard symbols may be indicated to a lower layer (eg, PHY layer) (of the node).

Meanwhile, the guard symbol may be an unused symbol based on a transition between the MT operation and the DU operation. Here, the term “transition” may be used interchangeably with the term “switching”.

For example, as described above, when the number of gap symbols (G_(S)) has a positive number, it may mean that the MT operates as follows.

-   -   When the DU is switched in the MT operation to start the DU         operation from symbol #n, the MT does not use as many symbols as         |G_(S)| before symbol #n as the MT timing reference.     -   When the DU performs the DU operation up to symbol #n and then         switches to the MT operation, the MT does not use as many         symbols as |G_(S)| after symbol #n as the MT timing reference.

Based on this, when describing the guard symbol, the guard symbol may mean a symbol that is not used for the IAB node MT in the slot(s) where the IAB node transitions between the IAB node MT and the IAB node DU.

Meanwhile, for example, the node may be a node supporting the MT operation and the DU operation. Since a more specific embodiment is the same as that described above (and will be described later), repeated description of overlapping content will be omitted for convenience of description.

For example, the MT operation may be an operation related to communication between the node and a parent node, and the DU operation may be an operation related to communication between the node and a child node or communication between the node and a terminal. Since a more specific embodiment is the same as that described above (and will be described later), repeated description of overlapping content will be omitted for convenience of description.

For example, the node may be an Integrated Access and Backhaul (IAB) node. Since a more specific embodiment is the same as that described above (and will be described later), repeated description of overlapping content will be omitted for convenience of description.

For example, the node may receive guard symbol information provided from a parent node. Here, for example, the provided guard symbol information may indicate the number of guard symbols for each combination of the MT operation and the DU operation. Since a more specific embodiment is the same as that described above (and will be described later), repeated description of overlapping content will be omitted for convenience of description.

As described above, the example in which the parent node informs the child node information about the guard symbol may correspond to an example of a kind of feedback method (For example, a method in which a child node transmits information about a guard symbol to a parent node, and in response, the parent node transmits information about a (to be applied) guard symbol to the child node).

On the other hand, as described above, there is not necessarily a kinship relationship between the example in which the MT transmits information about the number of guard symbols (and/or gap values) to the parent node and the example in which the parent node transmits information about the number of guard symbols (and/or gap values) (to be applied to the MT) to the MT. That is, it may operate as a separate embodiment between an embodiment in which the MT transmits information on the number of guard symbols (and/or gap values) to the parent node and an embodiment in which the parent node transmits information about the number (and/or gap value) of the guard symbols (to be applied to the MT) to the MT.

Of course, it is a natural example, an example, in which the parent node transmits information about the number (and/or gap values) of guard symbols (to be applied to the MT) to the MT after the MT transmits information about the number of guard symbols (and/or gap values) to the parent node, corresponds to an example provided herein.

On the other hand, the present embodiment may be implemented together with other examples described above (and to be described later) in combination with, for example, the embodiment of timing criteria to configure link availability, of determining the link availability of the MT (DU) with the link availability information of the DU (MT), of switching time between DU operation and MT operation, of operation in the time resource between the UL resource and the DL resource of the MT, of determining resource availability, and/or of examples of configuration, etc. for the number of specific guard symbol(s) (of course, this embodiment may also be implemented independently of other embodiments).

A.6. Configure the Number of Specific Guard Symbol(s)

The IAB node may be instructed from the parent DU through the MAC CE of the number of guard symbols to be applied during the transition between the MT operation and the DU operation within the IAB node. The number of such guard symbols may be configured differently according to a combination of the Tx/Rx direction of the MT and the Tx/Rx direction of the DU. In addition, it may be applied differently when transitioning from MT to DU and when transitioning from DU to MT.

The number of guard symbol(s) required when the IAB node transitions between the MT operation and the DU operation may vary depending on the Tx/Rx timing of the MT and the DU. Assuming that the IAB node applies the timing alignment case 1, the Tx/Rx timing of the IAB DU is the same among all IAB nodes, the same may be assumed between DU cells within the IAB node. However, in the case of the Tx/Rx timing of the IAB MT, it is affected by a propagation delay with the parent node. If the propagation delay between the MT-CCs in the same IAB node and the parent node is different, the Tx/Rx timing between “MT-CCs” may also be different. Therefore, the number of guard symbols required for each MT-CC in the IAB node may be different. When an IAB node is connected to two parent nodes using dual connectivity (DC), the propagation delay may be different for each carrier group (CG), and the number of required guard symbols may vary. If it is assumed that cells in the same CG are co-located, the difference in propagation delay between cells may be insignificant in the same CG, and thus the same number of guard symbols between MT-CCs may be assumed. However, when considering applying different timing alignment cases between IAB nodes later, or applying different Tx/Rx timings for each DU-cell within the IAB node and/or for each IAB node MT-CC, even within the same CG, the difference in Tx/Rx timing between MT-CCs may become large. The number of guard symbols required for each MT-CC may be different.

Considering the above characteristics, it is proposed that the ‘guard symbol MAC CE, which is a MAC CE transmitting guard symbol information, is transmitted as follows.

FIG. 39 schematically illustrates an example of a method of transmitting a guard symbol MAC CE.

According to FIG. 39 , the parent node may transmit the guard symbol MAC CE to the IAB node (S3610).

The IAB node may equally apply the information of the guard symbol MAC CE to all MT-CCs in the cell group including the MT-CC #N (S3620).

This is explained in more detail as follows.

-   -   Option 1: If the IAB node receives the guard symbol MAC CE         through a specific cell, the guard symbol MAC CE information may         be equally applied to all cells within the same CG as the         corresponding cell. In other words, if the IAB node receives the         guard symbol MAC CE through a specific MT-CC, the guard symbol         MAC CE information may be equally applied to all MT-CCs within         the same CG as the corresponding MT-CC.

When using this method, the same number of guard symbols is always applied to MT-CCs in the same CG. Therefore, when changing the number of guard symbols of all MT-CCs in the same CG, the parent node only needs to transmit the guard symbol MAC CE to one MT-CC.

FIG. 40 schematically illustrates another example of a method of transmitting a guard symbol MAC CE.

According to FIG. 40 , the parent node may transmit a guard symbol MAC CE to the IAB node (S4010).

The IAB node may apply the information of the guard symbol MAC CE only for MT-CC #N (S4020).

This will be described in more detail as follows.

-   -   Option 2: When the IAB node receives the guard symbol MAC CE         through a specific cell, the guard symbol MAC CE information may         be applied only to the corresponding cell. In other words, when         the IAB node receives the guard symbol MAC CE through a specific         MT-CC, the guard symbol MAC CE information may be applied only         to the corresponding MT-CC.

When using this method, a different number of guard symbol(s) may be applied for each MT-CC. However, the parent node transmits the guard symbol MAC CE to all MT-CCs requiring the guard symbol(s), when the number of guard symbols is changed, the guard symbol MAC CE is independently transmitted to all MT-CCs that need to be changed.

FIG. 41 schematically illustrates another example of a method of transmitting a guard symbol MAC CE.

According to FIG. 41 , the parent node may transmit the guard symbol MAC CE to the IAB node (S4110).

The IAB node may apply the information of the guard symbol MAC CE only to the MT-CC indicated by the guard symbol MAC CE (S4120).

This is explained in more detail as follows.

-   -   Option 3: When the IAB node receives the guard symbol MAC CE         through a specific cell, the guard symbol MAC CE information may         be applied to the cell indicated through the guard symbol MAC         CE. In other words, when the IAB node receives the guard symbol         MAC CE through a specific MT-CC, the guard symbol MAC CE         information may be applied to the MT-CC indicated through the         corresponding guard symbol MAC CE. To this end, information on a         cell to which the corresponding guard symbol MAC CE information         is applied may be included in the guard symbol MAC CE and         transmitted.

In the case of using this method, a different number of guard symbol(s) may be applied to each MT-CC, as in option 2 above. However, the parent node must transmit the guard symbol MAC CE to all MT-CCs requiring the guard symbol(s), when the number of guard symbols is changed, the guard symbol MAC CE must be independently transmitted to all MT-CCs that need to be changed.

FIG. 42 schematically illustrates another example of a method of transmitting a guard symbol MAC CE.

According to FIG. 42 , the parent node may transmit the guard symbol MAC CE to the IAB node through MT-CC #N (S4210).

The IAB node i) equally applies the information of the guard symbol MAC CE to all MT-CCs in the cell group including the MT-CC #N, or ii) only applies the information of the guard symbol MAC CE to MT-CC #N according to the value of the coverage indicator (S4220).

This is explained in more detail as follows.

-   -   Option 4: When the IAB node receives the guard symbol MAC CE         through a specific cell, according to instructions within the         guard symbol MAC CE, the guard symbol MAC CE information may be         equally applied to all cells within the same CG as the         corresponding cell (the specific cell) or may be applied only to         the corresponding cell (the specific cell). In other words, when         the IAB node receives the guard symbol MAC CE through a specific         MT-CC, according to instructions within the guard symbol MAC CE,         the guard symbol MAC CE information may be equally applied to         all MT-CCs within the same CG as the corresponding MT-CC (the         specific MT-CC) or may be applied only to the corresponding         MT-CC (the specific MT-CC).

For this purpose, an indication of whether the corresponding guard symbol MAC CE information is applied to all cells in the same CG or only the cell in which the guard symbol MAC CE is transmitted may be included in the guard symbol MAC CE. That is, for example, if the value of the 1-bit indicator in the guard symbol MAC CE is 0, this means that the corresponding guard symbol MAC CE information is equally applied to all cells in the same CG as the cell in which the guard symbol MAC CE is transmitted, if the value of the 1-bit indicator is 1, this may mean that the corresponding guard symbol MAC CE information is applied only to a cell in which the guard symbol MAC CE is transmitted.

Or for this, when the guard symbol MAC CE is transmitted to a specific cell (e.g., PCell), it is equally applied to all cells in the same CG, when transmitted to another cell (a cell other than the PCell, for example, the SCell), it may be applied only to the corresponding cell. That is, the range of cells to which the guard symbol MAC CE information is applied may be dependent on a cell to which the guard symbol MAC CE information is transmitted. Characteristically, this method can be applied only to a time point before each cell first receives the guard symbol MAC CE through the corresponding cell.

In case of using this method, the same number of guard symbols may be applied to all cells in the same CG efficiently, or a different number of guard symbols may be applied cell-specifically as needed.

FIG. 43 schematically illustrates another example of a method of transmitting a guard symbol MAC CE.

According to FIG. 43 , the parent node may transmit the guard symbol MAC CE to the IAB node through MT-CC #N (S4310).

The IAB node according to the value of the coverage indicator may i) equally apply the guard symbol MAC CE information to all MT-CCs in the cell group including the MT-CC indicated by the guard symbol MAC CE, or ii) only apply the information of the guard symbol MAC CE to the MT-CC indicated by the guard symbol MAC CE (S4320).

This is explained in more detail as follows.

-   -   Option 5: If the IAB node receives the guard symbol MAC CE         through a specific cell, according to instructions within the         guard symbol MAC CE, the guard symbol MAC CE information may be         equally applied to all cells within the same CG as the         corresponding cell (e.g., the specific cell or the cell         indicated by the guard symbol MAC CE) or may be applied only to         the indicated specific cell. In other words, when the IAB node         receives the guard symbol MAC CE through a specific MT-CC,         according to the instruction in the guard symbol MAC CE, the         guard symbol MAC CE information is equally applied to all MT-CCs         within the same CG as the corresponding MT-CC or can be applied         only to the indicated MT-CC.

For this purpose, an indication of whether the corresponding guard symbol MAC CE information is applied to all cells in the same CG or only to a specific cell may be included in the guard symbol MAC CE. When applied to a specific cell, cell information to which the guard symbol MAC CE information is additionally applied may be transmitted together.

Or, information on the cell ID to which the corresponding guard symbol MAC CE information is applied is informed through the guard symbol MAC CE, if the value indicated by the cell ID is 0 or a specific value, it may mean that it is applied to all cells in the same CG. In this case, the specific value may be, for example, a cell ID that is not designated as a serving cell of the IAB node.

Or, if information about the cell ID to which the guard symbol MAC CE information is applied is transmitted, the information is applied to the cell, if no information about cell ID is sent, it may mean that a cell to which the guard symbol MAC CE is transmitted is applied to all cells in the same CG. That is, the range of cells to which the guard symbol MAC CE information is applied may be dependent on whether information on a cell ID to which the guard symbol MAC CE information is applied is included in the guard symbol MAC CE.

When using these methods, if necessary, the same number of guard symbols may be efficiently applied to all cells in the same CG, or a different number of guard symbols may be applied specifically to cells.

FIG. 44 schematically illustrates another example of a method of transmitting a guard symbol MAC CE.

According to FIG. 44 , the parent node may transmit the guard symbol MAC CE to the IAB node through MT-CC #N (S4410).

The IAB node may equally apply the information of the guard symbol MAC CE to all MT-CCs in the same TAG as the MT-CC #N (S4420).

This is explained in more detail as follows.

-   -   Option 6: When the IAB node receives the guard symbol MAC CE         through a specific cell, the guard symbol MAC CE information may         be equally applied to all cells within the same TA group (TAG)         as the corresponding cell. In other words, when the IAB node         receives the guard symbol MAC CE through a specific MT-CC, the         guard symbol MAC CE information may be equally applied to all         MT-CCs within the same TAG as the corresponding MT-CC.

When using these methods, while applying the same number of guard symbols between cells that have the same propagation delay and require the same guard symbols, the different number of guard symbols may be applied between cells having different propagation delays and requiring different guard symbols.

FIG. 45 schematically illustrates another example of a method of transmitting a guard symbol MAC CE.

According to FIG. 45 , the parent node may transmit the guard symbol MAC CE to the IAB node through MT-CC #N (S4510).

The IAB node may equally apply the information of the guard symbol MAC CE to all MT-CCs in the TAG indicated by the guard symbol MAC CE (S4520).

This is explained in more detail as follows.

-   -   Option 7: When the IAB node receives the guard symbol MAC CE         through a specific cell, the guard symbol MAC CE information may         be equally applied to all cells within the TAG indicated through         the guard symbol MAC CE. In other words, when the IAB node         receives the guard symbol MAC CE through a specific MT-CC, the         same can be applied to all MT-CCs within the TAG indicated         through the guard symbol MAC CE. To this end, information on a         TAG to which the corresponding guard symbol MAC CE information         is applied may be included and transmitted in the guard symbol         MAC CE.

When using these methods, while applying the same number of guard symbols between cells that have the same propagation delay and require the same guard symbols, the different number of guard symbols may be applied between cells having different propagation delays and requiring different guard symbols.

Effects that can be obtained through specific examples of the present specification are not limited to the effects listed above. For example, various technical effects that a person having ordinary skill in the related art can understand or derive from the present specification may exist. Accordingly, the specific effects of the present specification are not limited to those explicitly described herein, and may include various effects that can be understood or derived from the technical characteristics of the present specification.

On the other hand, if the contents to which the above-described examples are applied from the point of view of the (child) node, it may be as follows.

The following drawings were created to explain a specific example of the present specification. Since the names of specific devices described in the drawings or the names of specific signals/messages/fields are presented by way of example, the technical features of the present specification are not limited to the specific names used in the following drawings.

FIG. 46 is a flowchart of a method of transmitting information about a guard symbol from the viewpoint of a (child) node, according to an embodiment of the present specification.

According to FIG. 46 , the node may determine the guard symbol information (S4610). Here, the guard symbol information may indicate the number of guard symbols related to switching between a mobile terminal (MT) operation and a distributed unit (DU) operation desired by the node, respectively. Since a more specific embodiment is the same as that described above (and will be described later), repeated description of overlapping content will be omitted for convenience of description.

The node may transmit the guard symbol information to the parent node (S4620). Here, the guard symbol may be an unused symbol based on a transition between the MT operation and the DU operation. Since a more specific embodiment is the same as that described above (and will be described later), repeated description of overlapping content will be omitted for convenience of description.

FIG. 47 is a block diagram of an example of an apparatus for transmitting information about a guard symbol from the viewpoint of a (child) node, according to an embodiment of the present specification.

Referring to FIG. 47 , the processor 4700 may include an information determining unit 4710 and an information transmitting unit 4720. Here, the processor may correspond to the processor of FIGS. 50 to 56 .

The information determining unit 4710 may be configured to determine the guard symbol information. Here, the guard symbol information may indicate the number of guard symbols related to switching between a mobile terminal (MT) operation and a distributed unit (DU) operation desired by the node, respectively. Since a more specific embodiment is the same as that described above (and will be described later), repeated description of overlapping content will be omitted for convenience of description.

The information transmitting unit 4720 may be configured to transmit the guard symbol information to a parent node. Here, the guard symbol may be an unused symbol based on a transition between the MT operation and the DU operation. Since a more specific embodiment is the same as that described above (and will be described later), repeated description of overlapping content will be omitted for convenience of description.

Meanwhile, although not shown separately, the present specification may also provide the following examples.

In one example, an apparatus may comprise at least one memory and at least one processor being operatively connected to the at least one memory, wherein the at least one processor is configured to determine guard symbol information, wherein the guard symbol information informs each of a number of guard symbols related to switching, which is desired by the node, between a mobile terminal (MT) operation and a distributed unit (DU) operation and control a transceiver to transmit, to a parent node, the guard symbol information, wherein the guard symbol is a symbol not used based on a transition between the MT operation and the DU operation.

In one example, at least one computer readable medium (CRM) may include instructions being executed by at least one processor, wherein the at least one processor is configured to determine guard symbol information, wherein the guard symbol information informs each of a number of guard symbols related to switching, which is desired by the node, between a mobile terminal (MT) operation and a distributed unit (DU) operation; and control a transceiver to transmit, to a parent node, the guard symbol information, wherein the guard symbol is a symbol not used based on a transition between the MT operation and the DU operation.

FIG. 48 is a flowchart of a method of receiving information about a guard symbol from the viewpoint of a (parent) node, according to an embodiment of the present specification.

Referring to FIG. 48 , the (parent) node may receive the guard symbol information from the child node (S4810). Here, the guard symbol information informs each of the number of guard symbols related to switching between a mobile terminal (MT) operation and a distributed unit (DU) operation desired by the node, the guard symbol may be an unused symbol based on a transition between the MT operation and the DU operation. Since a more specific embodiment is the same as that described above (and will be described later), repeated description of overlapping content will be omitted for convenience of description.

FIG. 49 is a block diagram of an example of an apparatus for receiving information about a guard symbol from the perspective of a (parent) node, according to an embodiment of the present specification.

Referring to FIG. 49 , the processor 4900 may include an information receiving unit 4910. Here, the processor may correspond to the processor of FIGS. 50 to 56 .

The information receiving unit 4910 may be configured to receive the guard symbol information from a child node. Here, the guard symbol information informs each of the number of guard symbols related to switching between a mobile terminal (MT) operation and a distributed unit (DU) operation desired by the node, the guard symbol may be an unused symbol based on a transition between the MT operation and the DU operation. Since a more specific embodiment is the same as that described above (and will be described later), repeated description of overlapping content will be omitted for convenience of description.

FIG. 50 shows an exemplary communication system (1), according to an embodiment of the present specification.

Referring to FIG. 50 , a communication system (1) to which various embodiments of the present specification are applied includes wireless devices, Base Stations (BSs), and a network. Herein, the wireless devices represent devices performing communication using Radio Access Technology (RAT) (e.g., 5G New RAT (NR)) or Long-Term Evolution (LTE)) and may be referred to as communication/radio/5G devices. The wireless devices may include, without being limited to, a robot (100 a), vehicles (100 b-1, 100 b-2), an eXtended Reality (XR) device (100 c), a hand-held device (100 d), a home appliance (100 e), an Internet of Things (IoT) device (100 f), and an Artificial Intelligence (AI) device/server (400). For example, the vehicles may include a vehicle having a wireless communication function, an autonomous vehicle, and a vehicle capable of performing communication between vehicles. Herein, the vehicles may include an Unmanned Aerial Vehicle (UAV) (e.g., a drone). The XR device may include an Augmented Reality (AR)/Virtual Reality (VR)/Mixed Reality (MR) device and may be implemented in the form of a Head-Mounted Device (HMD), a Head-Up Display (HUD) mounted in a vehicle, a television, a smartphone, a computer, a wearable device, a home appliance device, a digital signage, a vehicle, a robot, and so on. The hand-held device may include a smartphone, a smartpad, a wearable device (e.g., a smartwatch or a smartglasses), and a computer (e.g., a notebook). The home appliance may include a TV, a refrigerator, and a washing machine. The IoT device may include a sensor and a smartmeter. For example, the BSs and the network may be implemented as wireless devices and a specific wireless device (200 a) may operate as a BS/network node with respect to other wireless devices.

The wireless devices (100 a˜100 f) may be connected to the network (300) via the BSs (200). An Artificial Intelligence (AI) technology may be applied to the wireless devices (100 a-100 f) and the wireless devices (100 a-100 f) may be connected to the AI server (400) via the network (300). The network (300) may be configured using a 3G network, a 4G (e.g., LTE) network, or a 5G (e.g., NR) network. Although the wireless devices (100 a-100 f) may communicate with each other through the BSs (200)/network (300), the wireless devices (100 a-100 f) may perform direct communication (e.g., sidelink communication) with each other without passing through the BSs/network. For example, the vehicles (100 b-1, 100 b-2) may perform direct communication (e.g., Vehicle-to-Vehicle (V2V)/Vehicle-to-everything (V2X) communication). The IoT device (e.g., a sensor) may perform direct communication with other IoT devices (e.g., sensors) or other wireless devices (100 a-100 f).

Wireless communication/connections (150 a, 150 b, 150 c) may be established between the wireless devices (100 a˜100 f)/BS (200), or BS (200)/BS (200). Herein, the wireless communication/connections may be established through various RATs (e.g., 5G NR) such as uplink/downlink communication (150 a), sidelink communication (150 b) (or D2D communication), or inter BS communication (150 c) (e.g., relay, Integrated Access Backhaul (IAB)). The wireless devices and the BSs/the wireless devices may transmit/receive radio signals to/from each other through the wireless communication/connections (150 a, 150 b, 150 c). For example, the wireless communication/connections (150 a, 150 b, 150 c) may transmit/receive signals through various physical channels. For this, at least a part of various configuration information configuring processes, various signal processing processes (e.g., channel encoding/decoding, modulation/demodulation, and resource mapping/demapping), and resource allocating processes, for transmitting/receiving radio signals, may be performed based on the various proposals of the present specification.

Meanwhile, in NR, multiple numerologies (or subcarrier spacing (SCS)) for supporting various 5G services may be supported. For example, in case an SCS is 15 kHz, a wide area of the conventional cellular bands may be supported, and, in case an SCS is 30 kHz/60 kHz dense-urban, lower latency, and wider carrier bandwidth may be supported. In case the SCS is 60 kHz or higher, a bandwidth that is greater than 24.25 GHz may be used in order to overcome phase noise.

An NR frequency band may be defined as two different types of frequency ranges (FR1, FR2). The values of the frequency ranges may be changed (or varied), and, for example, the two different types of frequency ranges (FR1, FR2) may be as shown below in Table 16. Among the frequency ranges that are used in an NR system, FR1 may mean a “sub 6 GHz range”, and FR2 may mean an “above 6 GHz range” and may also be referred to as a millimeter wave (mmW).

TABLE 16 Frequency Range Corresponding Subcarrier designation frequency range Spacing FR1  450 MHz-6000 MHz 15, 30, 60 kHz FR2 24250 MHz-52600 MHz 60, 120, 240 kHz

As described above, the values of the frequency ranges in the INK system may be changed (or varied). For example, as shown below in Table 17, FR1 may include a band within a range of 410 MHz to 7125 MHz. More specifically, FR1 may include a frequency band of 6 GHz (or 5850, 5900, 5925 MHz, and so on) and higher. For example, a frequency band of 6 GHz (or 5850, 5900, 5925 MHz, and so on) and higher being included in FR1 may include an unlicensed band. The unlicensed band may be used for various purposes, e.g., the unlicensed band for vehicle-specific communication (e.g., automated driving).

TABLE 17 Frequency Range Corresponding Subcarrier designation frequency range Spacing FR1  410 MHz-7125 MHz 15, 30, 60 kHz FR2 24250 MHz-52600 MHz 60, 120, 240 kHz

Hereinafter, an example of wireless devices to which the present specification is applied will be described in detail. FIG. 51 shows an exemplary wireless device to which the present specification can be applied.

Referring to FIG. 51 , a first wireless device (100) and a second wireless device (200) may transmit radio signals through a variety of RATs (e.g., LTE, NR). Herein, {the first wireless device (100) and the second wireless device (200)} may correspond to {the wireless device (100 x) and the BS (200)} and/or {the wireless device (100 x) and the wireless device (100 x)} of FIG. 50 .

The first wireless device (100) may include one or more processors (102) and one or more memories (104) and additionally further include one or more transceivers (106) and/or one or more antennas (108). The processor(s) (102) may control the memory(s) (104) and/or the transceiver(s) (106) and may be configured to implement the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document. For example, the processor(s) (102) may process information within the memory(s) (104) to generate first information/signals and then transmit radio signals including the first information/signals through the transceiver(s) (106). The processor(s) (102) may receive radio signals including second information/signals through the transceiver (106) and then store information obtained by processing the second information/signals in the memory(s) (104). The memory(s) (104) may be connected to the processor(s) (102) and may store various information related to operations of the processor(s) (102). For example, the memory(s) (104) may store software code including instructions for performing a part or the entirety of processes controlled by the processor(s) (102) or for performing the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document. Herein, the processor(s) (102) and the memory(s) (104) may be a part of a communication modem/circuit/chip designed to implement RAT (e.g., LTE or NR). The transceiver(s) (106) may be connected to the processor(s) (102) and transmit and/or receive radio signals through one or more antennas (108). Each of the transceiver(s) (106) may include a transmitter and/or a receiver. The transceiver(s) (106) may be interchangeably used with Radio Frequency (RF) unit(s). In the present specification, the wireless device may represent a communication modem/circuit/chip.

The second wireless device (200) may include one or more processors (202) and one or more memories (204) and additionally further include one or more transceivers (206) and/or one or more antennas (208). The processor(s) (202) may control the memory(s) (204) and/or the transceiver(s) (206) and may be configured to implement the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document. For example, the processor(s) (202) may process information within the memory(s) (204) to generate third information/signals and then transmit radio signals including the third information/signals through the transceiver(s) (206). The processor(s) (202) may receive radio signals including fourth information/signals through the transceiver(s) (206) and then store information obtained by processing the fourth information/signals in the memory(s) (204). The memory(s) (204) may be connected to the processor(s) (202) and may store various information related to operations of the processor(s) (202). For example, the memory(s) (204) may store software code including instructions for performing a part or the entirety of processes controlled by the processor(s) (202) or for performing the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document. Herein, the processor(s) (202) and the memory(s) (204) may be a part of a communication modem/circuit/chip designed to implement RAT (e.g., LTE or NR). The transceiver(s) (206) may be connected to the processor(s) (202) and transmit and/or receive radio signals through one or more antennas (208). Each of the transceiver(s) (206) may include a transmitter and/or a receiver. The transceiver(s) (206) may be interchangeably used with RF transceiver(s). In the present specification, the wireless device may represent a communication modem/circuit/chip.

Hereinafter, hardware elements of the wireless devices (100, 200) will be described in more detail. One or more protocol layers may be implemented by, without being limited to, one or more processors (102, 202). For example, the one or more processors (102, 202) may implement one or more layers (e.g., functional layers such as PHY, MAC, RLC, PDCP, RRC, and SDAP). The one or more processors (102, 202) may generate one or more Protocol Data Units (PDUs) and/or one or more Service Data Unit (SDUs) according to the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document. The one or more processors (102, 202) may generate messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document. The one or more processors (102, 202) may generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document and provide the generated signals to the one or more transceivers (106, 206). The one or more processors (102, 202) may receive the signals (e.g., baseband signals) from the one or more transceivers (106, 206) and obtain the PDUs, SDUs, messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document.

The one or more processors (102, 202) may be referred to as controllers, microcontrollers, microprocessors, or microcomputers. The one or more processors (102, 202) may be implemented by hardware, firmware, software, or a combination thereof. As an example, one or more Application Specific Integrated Circuits (ASICs), one or more Digital Signal Processors (DSPs), one or more Digital Signal Processing Devices (DSPDs), one or more Programmable Logic Devices (PLDs), or one or more Field Programmable Gate Arrays (FPGAs) may be included in the one or more processors (102, 202). The descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document may be implemented using firmware or software and the firmware or software may be configured to include the modules, procedures, or functions. Firmware or software configured to perform the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document may be included in the one or more processors (102, 202) or stored in the one or more memories (104, 204) so as to be driven by the one or more processors (102, 202). The descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document may be implemented using firmware or software in the form of code, instructions, and/or a set of instructions.

The one or more memories (104, 204) may be connected to the one or more processors (102, 202) and store various types of data, signals, messages, information, programs, code, instructions, and/or commands. The one or more memories (104, 204) may be configured by Read-Only Memories (ROMs), Random Access Memories (RAMs), Electrically Erasable Programmable Read-Only Memories (EPROMs), flash memories, hard drives, registers, cash memories, computer-readable storage media, and/or combinations thereof. The one or more memories (104, 204) may be located at the interior and/or exterior of the one or more processors (102, 202). The one or more memories (104, 204) may be connected to the one or more processors (102, 202) through various technologies such as wired or wireless connection.

The one or more transceivers (106, 206) may transmit user data, control information, and/or radio signals/channels, mentioned in the methods and/or operational flowcharts of this document, to one or more other devices. The one or more transceivers (106, 206) may receive user data, control information, and/or radio signals/channels, mentioned in the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document, from one or more other devices. For example, the one or more transceivers (106, 206) may be connected to the one or more processors (102, 202) and transmit and receive radio signals. For example, the one or more processors (102, 202) may perform control so that the one or more transceivers (106, 206) may transmit user data, control information, or radio signals to one or more other devices. The one or more processors (102, 202) may perform control so that the one or more transceivers (106, 206) may receive user data, control information, or radio signals from one or more other devices. The one or more transceivers (106, 206) may be connected to the one or more antennas (108, 208) and the one or more transceivers (106, 206) may be configured to transmit and receive user data, control information, and/or radio signals/channels, mentioned in the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document, through the one or more antennas (108, 208). In this document, the one or more antennas may be a plurality of physical antennas or a plurality of logical antennas (e.g., antenna ports). The one or more transceivers (106, 206) may convert received radio signals/channels, and so on, from RF band signals into baseband signals in order to process received user data, control information, radio signals/channels, and so on, using the one or more processors (102, 202). The one or more transceivers (106, 206) may convert the user data, control information, radio signals/channels, and so on, processed using the one or more processors (102, 202) from the base band signals into the RF band signals. For this, the one or more transceivers (106, 206) may include (analog) oscillators and/or filters.

FIG. 52 shows another example of a wireless device applicable to the present specification.

According to FIG. 52 , the wireless device may include at least one processor (102, 202), at least one memory (104, 204), at least one transceiver (106, 206), and/or one or more antennas (108, 208).

As a difference between the example of the wireless device described above in FIG. 51 and the example of the wireless device in FIG. 52 , in FIG. 51 , the processors 102 and 202 and the memories 104 and 204 are separated, but in the example of FIG. 52 , the memories 104 and 204 are included in the processors 102 and 202.

Here, a detailed description of the processors 102 and 202, the memories 104 and 204, the transceivers 106 and 206, and the one or more antennas 108 and 208 is as described above, in order to avoid unnecessary repetition of description, description of repeated description will be omitted.

Hereinafter, an example of a signal processing circuit to which the present specification is applied will be described in detail.

FIG. 53 shows a signal process circuit for a transmission signal according to an embodiment of the present specification.

Referring to FIG. 53 , a signal processing circuit (1000) may include scramblers (1010), modulators (1020), a layer mapper (1030), a precoder (1040), resource mappers (1050), and signal generators (1060). An operation/function of FIG. 53 may be performed, without being limited to, the processors (102, 202) and/or the transceivers (106, 206) of FIG. 51 . Hardware elements of FIG. 53 may be implemented by the processors (102, 202) and/or the transceivers (106, 206) of FIG. 51 . For example, blocks 1010-1060 may be implemented by the processors (102, 202) of FIG. 51 . Alternatively, the blocks 1010-1050 may be implemented by the processors (102, 202) of FIG. 51 and the block 1060 may be implemented by the transceivers (106, 206) of FIG. 51 .

Codewords may be converted into radio signals via the signal processing circuit (1000) of FIG. 53 . Herein, the codewords are encoded bit sequences of information blocks. The information blocks may include transport blocks (e.g., a UL-SCH transport block, a DL-SCH transport block). The radio signals may be transmitted through various physical channels (e.g., a PUSCH and a PDSCH).

More specifically, the codewords may be converted into scrambled bit sequences by the scramblers (1010). Scramble sequences used for scrambling may be generated based on an initialization value, and the initialization value may include ID information of a wireless device. The scrambled bit sequences may be modulated to modulation symbol sequences by the modulators (1020). A modulation scheme may include pi/2-Binary Phase Shift Keying (pi/2-BPSK), m-Phase Shift Keying (m-PSK), and m-Quadrature Amplitude Modulation (m-QAM). Complex modulation symbol sequences may be mapped to one or more transport layers by the layer mapper (1030). Modulation symbols of each transport layer may be mapped (precoded) to corresponding antenna port(s) by the precoder (1040). Outputs z of the precoder (1040) may be obtained by multiplying outputs y of the layer mapper (1030) by an N*M precoding matrix W. Herein, N is the number of antenna ports, and M is the number of transport layers. The precoder (1040) may perform precoding after performing transform precoding (e.g., DFT) for complex modulation symbols. Additionally, the precoder (1040) may perform precoding without performing transform precoding.

The resource mappers (1050) may map modulation symbols of each antenna port to time-frequency resources. The time-frequency resources may include a plurality of symbols (e.g., a CP-OFDMA symbols and DFT-s-OFDMA symbols) in the time domain and a plurality of subcarriers in the frequency domain. The signal generators (1060) may generate radio signals from the mapped modulation symbols and the generated radio signals may be transmitted to other devices through each antenna. For this purpose, the signal generators (1060) may include Inverse Fast Fourier Transform (IFFT) modules, Cyclic Prefix (CP) inserters, Digital-to-Analog Converters (DACs), frequency uplink converters, and so on.

Signal processing procedures for a signal received in the wireless device may be configured in a reverse manner of the signal processing procedures (1010-1060) of FIG. 53 . For example, the wireless devices (e.g., 100, 200 of FIG. 51 ) may receive radio signals from the exterior through the antenna ports/transceivers. The received radio signals may be converted into baseband signals through signal restorers. For this, the signal restorers may include frequency downlink converters, Analog-to-Digital Converters (ADCs), CP remover, and Fast Fourier Transform (FFT) modules. Subsequently, the baseband signals may be restored to codewords through a resource demapping procedure, a postcoding procedure, a demodulation processor, and a descrambling procedure. The codewords may be restored to original information blocks through decoding. Therefore, a signal processing circuit (not shown) for a reception signal may include signal restorers, resource demappers, a postcoder, demodulators, descramblers, and decoders.

Hereinafter, a usage example of the wireless to which the present specification is applied will be described in detail.

FIG. 54 shows another example of a wireless device according to an embodiment of the present specification. The wireless device may be implemented in various forms according to a use-case/service (refer to FIG. 50 ).

Referring to FIG. 54 , wireless devices (100, 200) may correspond to the wireless devices (100, 200) of FIG. 51 and may be configured by various elements, components, units/portions, and/or modules. For example, each of the wireless devices (100, 200) may include a communication unit (110), a control unit (120), a memory unit (130), and additional components (140). The communication unit may include a communication circuit (112) and transceiver(s) (114). For example, the communication circuit (112) may include the one or more processors (102, 202) and/or the one or more memories (104, 204) of FIG. 51 . For example, the transceiver(s) (114) may include the one or more transceivers (106, 206) and/or the one or more antennas (108, 208) of FIG. 51 . The control unit (120) is electrically connected to the communication unit (110), the memory (130), and the additional components (140) and controls overall operation of the wireless devices. For example, the control unit (120) may control an electric/mechanical operation of the wireless device based on programs/code/instructions/information stored in the memory unit (130). The control unit (120) may transmit the information stored in the memory unit (130) to the exterior (e.g., other communication devices) via the communication unit (110) through a wireless/wired interface or store, in the memory unit (130), information received through the wireless/wired interface from the exterior (e.g., other communication devices) via the communication unit (110).

The additional components (140) may be variously configured according to types of wireless devices. For example, the additional components (140) may include at least one of a power unit/battery, input/output (I/O) unit, a driving unit, and a computing unit. The wireless device may be implemented in the form of, without being limited to, the robot (100 a of FIG. 50 ), the vehicles (100 b-1, 100 b-2 of FIG. 50 ), the XR device (100 c of FIG. 50 ), the hand-held device (100 d of FIG. 50 ), the home appliance (100 e of FIG. 50 ), the IoT device (100 f of FIG. 50 ), a digital broadcast terminal, a hologram device, a public safety device, an MTC device, a medicine device, a fintech device (or a finance device), a security device, a climate/environment device, the AI server/device (400 of FIG. 50 ), the BSs (200 of FIG. 50 ), a network node, and so on. The wireless device may be used in a mobile or fixed place according to a usage-example/service.

In FIG. 54 , the entirety of the various elements, components, units/portions, and/or modules in the wireless devices (100, 200) may be connected to each other through a wired interface or at least a part thereof may be wirelessly connected through the communication unit (110). For example, in each of the wireless devices (100, 200), the control unit (120) and the communication unit (110) may be connected by wire and the control unit (120) and first units (e.g., 130, 140) may be wirelessly connected through the communication unit (110). Each element, component, unit/portion, and/or module within the wireless devices (100, 200) may further include one or more elements. For example, the control unit (120) may be configured by a set of one or more processors. As an example, the control unit (120) may be configured by a set of a communication control processor, an application processor, an Electronic Control Unit (ECU), a graphical processing unit, and a memory control processor. As another example, the memory (130) may be configured by a Random Access Memory (RAM), a Dynamic RAM (DRAM), a Read Only Memory (ROM)), a flash memory, a volatile memory, a non-volatile memory, and/or a combination thereof.

Hereinafter, an example of implementing FIG. 54 will be described in detail with reference to the drawings.

FIG. 55 shows a hand-held device to which the present specification is applied. The hand-held device may include a smartphone, a smartpad, a wearable device (e.g., a smartwatch or a smartglasses), or a portable computer (e.g., a notebook). The hand-held device may be referred to as a mobile station (MS), a user terminal (UT), a Mobile Subscriber Station (MSS), a Subscriber Station (SS), an Advanced Mobile Station (AMS), or a Wireless Terminal (WT).

Referring to FIG. 55 , a hand-held device (100) may include an antenna unit (108), a communication unit (110), a control unit (120), a memory unit (130), a power supply unit (140 a), an interface unit (140 b), and an I/O unit (140 c). The antenna unit (108) may be configured as a part of the communication unit (110). Blocks 110-130/140 a˜140 c correspond to the blocks 110˜130/140 of FIG. 54 , respectively.

The communication unit (110) may transmit and receive signals (e.g., data and control signals) to and from other wireless devices or BSs. The control unit (120) may perform various operations by controlling constituent elements of the hand-held device (100). The control unit (120) may include an Application Processor (AP). The memory unit (130) may store data/parameters/programs/code/instructions (or commands) needed to drive the hand-held device (100). The memory unit (130) may store input/output data/information. The power supply unit (140 a) may supply power to the hand-held device (100) and include a wired/wireless charging circuit, a battery, and so on. The interface unit (140 b) may support connection of the hand-held device (100) to other external devices. The interface unit (140 b) may include various ports (e.g., an audio I/O port and a video I/O port) for connection with external devices. The I/O unit (140 c) may input or output video information/signals, audio information/signals, data, and/or information input by a user. The I/O unit (140 c) may include a camera, a microphone, a user input unit, a display unit (140 d), a speaker, and/or a haptic module.

As an example, in the case of data communication, the I/O unit (140 c) may obtain information/signals (e.g., touch, text, voice, images, or video) input by a user and the obtained information/signals may be stored in the memory unit (130). The communication unit (110) may convert the information/signals stored in the memory into radio signals and transmit the converted radio signals to other wireless devices directly or to a BS. The communication unit (110) may receive radio signals from other wireless devices or the BS and then restore the received radio signals into original information/signals. The restored information/signals may be stored in the memory unit (130) and may be output as various types (e.g., text, voice, images, video, or haptic) through the I/O unit (140 c).

FIG. 56 shows a vehicle or an autonomous vehicle to which the present specification is applied. The vehicle or autonomous vehicle may be implemented by a mobile robot, a car, a train, a manned/unmanned Aerial Vehicle (AV), a ship, and so on.

Referring to FIG. 56 , a vehicle or autonomous vehicle (100) may include an antenna unit (108), a communication unit (110), a control unit (120), a driving unit (140 a), a power supply unit (140 b), a sensor unit (140 c), and an autonomous driving unit (140 d). The antenna unit (108) may be configured as a part of the communication unit (110). The blocks 110/130/140 a-140 d correspond to the blocks 110/130/140 of FIG. 54 , respectively.

The communication unit (110) may transmit and receive signals (e.g., data and control signals) to and from external devices such as other vehicles, BSs (e.g., gNBs and road side units), and servers. The control unit (120) may perform various operations by controlling elements of the vehicle or the autonomous vehicle (100). The control unit (120) may include an Electronic Control Unit (ECU). The driving unit (140 a) may cause the vehicle or the autonomous vehicle (100) to drive on a road. The driving unit (140 a) may include an engine, a motor, a powertrain, a wheel, a brake, a steering device, and so on. The power supply unit (140 b) may supply power to the vehicle or the autonomous vehicle (100) and include a wired/wireless charging circuit, a battery, and so on. The sensor unit (140 c) may obtain a vehicle state, ambient environment information, user information, and so on. The sensor unit (140 c) may include an Inertial Measurement Unit (IMU) sensor, a collision sensor, a wheel sensor, a speed sensor, a slope sensor, a weight sensor, a heading sensor, a position module, a vehicle forward/backward sensor, a battery sensor, a fuel sensor, a tire sensor, a steering sensor, a temperature sensor, a humidity sensor, an ultrasonic sensor, an illumination sensor, a pedal position sensor, and so on. The autonomous driving unit (140 d) may implement technology for maintaining a lane on which a vehicle is driving, technology for automatically adjusting speed, such as adaptive cruise control, technology for autonomously driving along a determined path, technology for driving by automatically setting a path if a destination is set, and so on.

For example, the communication unit (110) may receive map data, traffic information data, and so on, from an external server. The autonomous driving unit (140 d) may generate an autonomous driving path and a driving plan from the obtained data. The control unit (120) may control the driving unit (140 a) such that the vehicle or the autonomous vehicle (100) may move along the autonomous driving path according to the driving plan (e.g., speed/direction control). In the middle of autonomous driving, the communication unit (110) may aperiodically/periodically obtain recent traffic information data from the external server and obtain surrounding traffic information data from neighboring vehicles. In the middle of autonomous driving, the sensor unit (140 c) may obtain a vehicle state and/or surrounding environment information. The autonomous driving unit (140 d) may update the autonomous driving path and the driving plan based on the newly obtained data/information. The communication unit (110) may transfer information on a vehicle position, the autonomous driving path, and/or the driving plan to the external server. The external server may predict traffic information data using AI technology, and so on, based on the information collected from vehicles or autonomous vehicles and provide the predicted traffic information data to the vehicles or the autonomous vehicles.

Hereinafter, an example of next-generation communication to which embodiments of the present specification can be applied will be described.

FIG. 57 is a diagram illustrating an example of a communication structure that can be provided in a 6G system.

6G systems are expected to have 50 times higher simultaneous wireless connectivity than 5G wireless systems. URLLC, a key feature of 5G, will become an even more important technology by providing an end-to-end delay of less than 1 ms in 6G communication. 6G systems will have much better volumetric spectral efficiencies as opposed to frequently used areal spectral efficiencies. The 6G system can provide very long battery life and advanced battery technology for energy harvesting, so mobile devices will not need to be charged separately in the 6G system. New network characteristics in 6G may be as follows.

-   -   Satellites integrated network: 6G is expected to be integrated         with satellites to provide a global mobile cohort. The         integration of terrestrial, satellite and public networks into         one wireless communication system is very important for 6G.     -   Connected intelligence: Unlike previous generations of wireless         communication systems, 6G is revolutionary and will update the         wireless evolution from “connected things” to “connected         intelligence”. AI may be applied in each step of a communication         procedure (or each procedure of signal processing to be         described later).     -   Seamless integration wireless information and energy transfer:         The 6G wireless network will deliver power to charge the         batteries of devices such as smartphones and sensors. Therefore,         wireless information and energy transfer (WIET) will be         integrated.     -   Ubiquitous super 3D connectivity: Access to networks and core         network functions of drones and very low Earth orbit satellites         will create super 3D connectivity in 6G ubiquitous.

Some general requirements in the new network characteristics of 6G may be as follows.

-   -   Small cell networks: The idea of a small cell network was         introduced to improve the received signal quality as a result of         improved throughput, energy efficiency and spectral efficiency         in cellular systems. As a result, small cell networks are         essential characteristics for communication systems beyond 5G         and beyond 5G (5 GB). Accordingly, the 6G communication system         also adopts the characteristics of the small cell network.     -   Ultra-dense heterogeneous network: Ultra-high-density         heterogeneous networks will be another important characteristic         of 6G communication systems. A multi-tier network composed of         heterogeneous networks improves overall QoS and reduces costs.     -   High-capacity backhaul: A backhaul connection is characterized         as a high-capacity backhaul network to support high-volume         traffic. High-speed fiber optics and free-space optics (FSO)         systems may be possible solutions to this problem.     -   Radar technology integrated with mobile technology:         High-precision localization (or location-based service) through         communication is one of the functions of the 6G wireless         communication system. Therefore, the radar system will be         integrated with the 6G network.     -   Softwarization and virtualization: Softening and virtualization         are two important features that underlie the design process in 5         GB networks to ensure flexibility, reconfigurability and         programmability. In addition, billions of devices can be shared         in a shared physical infrastructure.

Claims in the present specification may be combined in various ways. For instance, technical features in method claims of the present specification may be combined to be implemented or performed in an apparatus (or device), and technical features in apparatus claims may be combined to be implemented or performed in a method. Further, technical features in method claim(s) and apparatus claim(s) may be combined to be implemented or performed in an apparatus. Further, technical features in method claim(s) and apparatus claim(s) may be combined to be implemented or performed in a method. 

What is claimed is:
 1. A method for an integrated access and backhaul (IAB) node in a wireless communication system, the method performed by the IAB node and comprising: generating a desired guard symbols MAC CE; and wherein the IAB node informs a parent IAB node about a number of guard symbols desired via the desired guard symbols MAC CE, wherein the desired guard symbols MAC CE includes guard symbol information, and wherein the guard symbol information indicates the number of guard symbols for switching between a mobile terminal (MT) operation and a distributed unit (DU) operation.
 2. The method of claim 1, wherein the IAB node supports the MT operation and the DU operation.
 3. The method of claim 1, wherein the MT operation is an operation related to a communication between the IAB node and parent IAB node, and wherein the DU operation is an operation related to a communication between the IAB node and a next-hop IAB node or a communication between the IAB node and a user equipment (UE).
 4. The method of claim 1, wherein the desired guard symbols MAC CE includes first information and second information, wherein the first information is information for a number of guard symbols for a transition from the MT operation to the DU operation, wherein the second information is information for a number of guard symbols for a transition from the DU operation to the MT operation.
 5. The method of claim 4, wherein the MT operation is at least one of a MT transmission (TX) and a MT reception (RX), and wherein the DU operation is at least one of a DU TX and a DU RX.
 6. The method of claim 5, wherein the first information includes at least one of: information for a number of guard symbols for a transition from the MT RX to the DU TX, information for a number of guard symbols for a transition from the MT RX to the DU RX, information for a number of guard symbols for a transition from the MT TX to the DU TX, or information for a number of guard symbols for a transition from the MT TX to the DU RX.
 7. The method of claim 5, wherein the second information includes at least one of: information for a number of guard symbols for a transition from the DU TX to the MT RX, information for a number of guard symbols for a transition from the DU TX to the MT TX, information for a number of guard symbols for a transition from the DU RX to the MT RX, or information for a number of guard symbols for a transition from the DU RX to the MT TX.
 8. The method of claim 1, wherein the IAB node transmits the desired guard symbols MAC CE to the parent IAB node.
 9. An integrated access and backhaul (IAB) node comprising: a transceiver; at least one memory; and at least one processor being operatively connected to the at least one memory and the transceiver, wherein the at least one processor is configured to: generate a desired guard symbols MAC CE; and wherein the IAB node informs a parent IAB node about a number of guard symbols desired via the desired guard symbols MAC CE, wherein the desired guard symbols MAC CE includes guard symbol information, and wherein the guard symbol information indicates the number of guard symbols for switching between a mobile terminal (MT) operation and a distributed unit (DU) operation.
 10. An apparatus comprising: at least one memory; and at least one processor being operatively connected to the at least one memory, wherein the at least one processor is configured to: generate a desired guard symbols MAC CE; and wherein the IAB node informs a parent IAB node about a number of guard symbols desired via the desired guard symbols MAC CE, wherein the desired guard symbols MAC CE includes guard symbol information, and wherein the guard symbol information indicates the number of guard symbols for switching between a mobile terminal (MT) operation and a distributed unit (DU) operation. 